clawpowers 1.1.1 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -0
- package/bin/clawpowers.js +227 -8
- package/docs/launch-images/25-skills-breakdown.jpg +0 -0
- package/docs/launch-images/clawpowers-vs-superpowers.jpg +0 -0
- package/docs/launch-images/economic-code-optimization.jpg +0 -0
- package/docs/launch-images/native-vs-bridge-2.jpg +0 -0
- package/docs/launch-images/native-vs-bridge.jpg +0 -0
- package/docs/launch-images/ultimate-stack.jpg +0 -0
- package/package.json +1 -1
- package/runtime/demo/x402-mock-server.js +230 -0
- package/runtime/init.js +40 -2
- package/runtime/init.sh +34 -1
- package/runtime/payments/ledger.js +305 -0
- package/runtime/payments/ledger.sh +262 -0
- package/skill.json +14 -3
- package/skills/agent-payments/SKILL.md +68 -0
- package/skills/market-intelligence/SKILL.md +35 -0
- package/skills/security-audit/SKILL.md +45 -0
- package/skills/using-clawpowers/SKILL.md +3 -0
|
@@ -222,6 +222,41 @@ Score identified opportunities on 4 dimensions:
|
|
|
222
222
|
[List all sources with access dates]
|
|
223
223
|
```
|
|
224
224
|
|
|
225
|
+
### Premium Data Sources (x402-Aware)
|
|
226
|
+
|
|
227
|
+
Market research frequently encounters paid API boundaries — academic paper databases, financial data APIs, patent registries, and proprietary datasets. ClawPowers routes these through the payment decision pipeline so you stay in control.
|
|
228
|
+
|
|
229
|
+
**When research hits a 402 Payment Required response:**
|
|
230
|
+
|
|
231
|
+
1. **Payments disabled** → Log the encounter and skip. Report: `[payment gate: skipped — payments.enabled=false]`. Continue with free alternatives.
|
|
232
|
+
2. **Dry-run mode** → Log what would happen. Report: `[dry-run: would pay $0.05 USDC on base to access financial data API]`. No funds move. Use `npx clawpowers payments log` to review.
|
|
233
|
+
3. **Live mode** → Evaluate against spending policy. If the cost fits within per-transaction and daily limits, pay autonomously and retry the request with payment proof.
|
|
234
|
+
|
|
235
|
+
**Example premium sources the payment pipeline handles:**
|
|
236
|
+
|
|
237
|
+
| Source | Typical Cost | Value |
|
|
238
|
+
|--------|-------------|-------|
|
|
239
|
+
| Financial data APIs (real-time prices, fundamentals) | $0.01–$0.10/request | Live market data for opportunity scoring |
|
|
240
|
+
| Patent databases (full-text search) | $0.05–$0.50/query | IP landscape analysis |
|
|
241
|
+
| Academic papers (behind paywalls) | $0.03–$0.30/paper | Early technology signal research |
|
|
242
|
+
| Proprietary analyst datasets | $0.10–$2.00/query | Competitive benchmarking |
|
|
243
|
+
|
|
244
|
+
**Configuration check before any paid research step:**
|
|
245
|
+
|
|
246
|
+
```bash
|
|
247
|
+
# Check current payment mode before hitting paid sources
|
|
248
|
+
cat ~/.clawpowers/config.json | grep -A2 '"payments"'
|
|
249
|
+
|
|
250
|
+
# Review what payment gates have been hit during this research session
|
|
251
|
+
npx clawpowers payments log --limit 10
|
|
252
|
+
```
|
|
253
|
+
|
|
254
|
+
**Recommended workflow:**
|
|
255
|
+
1. Run free sources first (GitHub API, npm stats, HN search, public web)
|
|
256
|
+
2. When a free source hits a 402 wall, check if the premium data is decision-critical
|
|
257
|
+
3. If yes and payments are enabled: let the pipeline evaluate and pay if policy allows
|
|
258
|
+
4. If no: log the gap and note it in the intelligence report as a confidence gap
|
|
259
|
+
|
|
225
260
|
## ClawPowers Enhancement
|
|
226
261
|
|
|
227
262
|
When `~/.clawpowers/` runtime is initialized:
|
|
@@ -265,6 +265,51 @@ trivy fs . --severity HIGH,CRITICAL
|
|
|
265
265
|
bandit -r src/ -ll
|
|
266
266
|
```
|
|
267
267
|
|
|
268
|
+
### Premium Scanner Escalation
|
|
269
|
+
|
|
270
|
+
The default audit pipeline uses **free local scanners**: `npm audit`, `gitleaks`, `trivy`, `bandit`, and `semgrep`. These cover the vast majority of findings and require no payment.
|
|
271
|
+
|
|
272
|
+
When free scanners surface critical or high-severity findings, premium scanners can provide deeper analysis: broader CVE databases, behavioral analysis, license compliance, supply-chain attack detection, and exploit chain mapping.
|
|
273
|
+
|
|
274
|
+
**Payment gate logic for scanner escalation:**
|
|
275
|
+
|
|
276
|
+
| Config state | Behavior |
|
|
277
|
+
|-------------|---------|
|
|
278
|
+
| `payments.enabled = false` | Log the premium scanner option. Skip it. Proceed with free scan results only. |
|
|
279
|
+
| `payments.mode = "dry_run"` | Log what would happen: `[dry-run: would pay $0.05 for Snyk deep scan]`. No charge. |
|
|
280
|
+
| `payments.mode = "live"` | Evaluate cost vs. severity. If cost fits policy limits and severity is Critical/High, pay and run the premium scan. |
|
|
281
|
+
|
|
282
|
+
**Example escalation scenarios:**
|
|
283
|
+
|
|
284
|
+
```
|
|
285
|
+
Trivy found 2 critical vulns in base image.
|
|
286
|
+
Premium scanner (Snyk container) available for $0.05.
|
|
287
|
+
[dry-run: would pay — severity=critical, cost=$0.05 < per_tx_limit=$0.10]
|
|
288
|
+
```
|
|
289
|
+
|
|
290
|
+
```
|
|
291
|
+
gitleaks found 0 secrets in current HEAD.
|
|
292
|
+
Premium deep-history scan available for $0.20.
|
|
293
|
+
[skipped — payments.enabled=false]
|
|
294
|
+
```
|
|
295
|
+
|
|
296
|
+
**When to escalate:**
|
|
297
|
+
- `CRITICAL` findings from free scanners → always consider premium for exploit chain analysis
|
|
298
|
+
- `HIGH` findings with active CVEs → premium scanner may have fresher signature database
|
|
299
|
+
- Pre-production release gates → deep scan is worth the cost
|
|
300
|
+
- Compliance requirements (SOC 2, PCI) → premium scanners generate compliance-ready reports
|
|
301
|
+
|
|
302
|
+
**Check payment config before escalating:**
|
|
303
|
+
|
|
304
|
+
```bash
|
|
305
|
+
cat ~/.clawpowers/config.json | grep -A8 '"payments"'
|
|
306
|
+
|
|
307
|
+
# After audit session, review any payment decisions made
|
|
308
|
+
npx clawpowers payments log
|
|
309
|
+
```
|
|
310
|
+
|
|
311
|
+
**Escalation is always optional.** The free scanner suite is production-grade. Premium escalation improves coverage at the margin — it never replaces the free baseline.
|
|
312
|
+
|
|
268
313
|
## ClawPowers Enhancement
|
|
269
314
|
|
|
270
315
|
When `~/.clawpowers/` runtime is initialized:
|
|
@@ -53,6 +53,9 @@ Skills activate automatically when you recognize a matching task pattern. You do
|
|
|
53
53
|
| Need to create a new skill | `writing-skills` |
|
|
54
54
|
| Multiple independent tasks that can run concurrently | `dispatching-parallel-agents` |
|
|
55
55
|
| Making a payment or calling a paid API | `agent-payments` |
|
|
56
|
+
| "setup payments" / "enable wallet" / "configure spending" | `agent-payments` → `npx clawpowers payments setup` |
|
|
57
|
+
| "demo x402" / "test payments" / "mock merchant" | `npx clawpowers demo x402` |
|
|
58
|
+
| "payment log" / "spending history" | `npx clawpowers payments log` |
|
|
56
59
|
| Checking code/containers for vulnerabilities | `security-audit` |
|
|
57
60
|
| Writing blog posts, docs, or social content | `content-pipeline` |
|
|
58
61
|
| Need to understand how to learn something effectively | `learn-how-to-learn` |
|