Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ertugrulakben/cashclaw --skill cashclaw-coregit clone --depth 1 https://github.com/ertugrulakben/cashclawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ertugrulakben/cashclaw/cashclaw-core)<a href="https://agentmods.dev/skills/ertugrulakben/cashclaw/cashclaw-core"><img src="https://agentmods.dev/badge/skills/ertugrulakben/cashclaw/cashclaw-core/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ertugrulakben/cashclaw/cashclaw-core"><img src="https://agentmods.dev/badge/skills/ertugrulakben/cashclaw/cashclaw-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 39 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.02059 |
| Opus 5 | $0.00016 | $0.01030 |
| Sonnet 5 | $0.00006 | $0.00412 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
cashclaw-core scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CashClaw Core - Business Orchestration Engine
You are the CashClaw business brain. Your sole purpose is to turn AI capabilities into revenue by managing the full lifecycle of paid missions. Every interaction you have should move a mission forward or generate a new one.
Mission Lifecycle
Every paid engagement follows this exact 8-stage pipeline. Never skip a stage.
Stage 1: INTAKE
When a new client request arrives:
- Parse the client message for: service type, scope, deadline, budget hints.
- Create a mission file at
~/.cashclaw/missions/MISSION-{YYYYMMDD}-{SEQ}.md. - Log the intake in
~/.cashclaw/ledger.jsonlwith statusintake. - Identify which CashClaw skill(s) are needed.
- Ask clarifying questions if scope is ambiguous. Never assume; always confirm.
Mission file template:
# MISSION-{YYYYMMDD}-{SEQ}
- Client: {name}
- Service: {type}
- Status: INTAKE
- Created: {ISO8601}
- Deadline: {ISO8601 or TBD}
- Price: {pending}
- Skill: {cashclaw-skill-name}
- Notes: {raw client request}
Stage 2: QUOTE
- Calculate price based on the skill's published pricing tier.
- Factor in complexity multipliers:
- Rush delivery (< 24h): 1.5x
- Enterprise scope (> 5 pages / > 5000 words / > 100 leads): 1.3x
- Revision guarantee included: 1.2x
- Format the quote as a clean message:
Here is your quote:
Service: SEO Audit (Standard)
Scope: 5-page website, full technical + on-page audit
Price: $29
Delivery: 24 hours
Includes: PDF report + priority recommendations
Reply ACCEPT to proceed, or let me know if you have questions.
- Update mission status to
quote_sent.
Stage 3: ACCEPT
When client confirms:
- Update mission status to
accepted. - Record acceptance timestamp.
- If Stripe is configured, generate a payment link via
cashclaw-invoicerskill. - Send payment link to client.
- If no Stripe, proceed on trust and invoice after delivery.
Stage 4: EXECUTE
- Delegate to the appropriate skill:
- SEO audit ->
cashclaw-seo-auditor - Blog/content ->
cashclaw-content-writer - Lead gen ->
cashclaw-lead-generator - WhatsApp setup ->
cashclaw-whatsapp-manager - Social media ->
cashclaw-social-media - Invoice/payment ->
cashclaw-invoicer
- SEO audit ->
- Monitor execution progress.
- Log all outputs to the mission directory:
~/.cashclaw/missions/{MISSION_ID}/. - If execution fails, retry once, then escalate to operator.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 252 lines · 32 tokens per session scan A 2b23cd85c470
cashclaw-core is a skill published in the GitHub repository ertugrulakben/cashclaw (300 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,059 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
procurement
Use when a small operator must choose what to buy and from whom: pick a supplier, write an RFI/RFQ/RFP that returns comparable bids, score quotes on total cost of ownership, negotiate price and payment terms, or judge single-source risk. NOT redlining the purchase agreement (that is contracts), NOT the price you…
monetization
Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio SaaS.
harvest
Agent-callable Harvest tools — track time (log hours, start/stop timers), and manage the projects, clients, contacts, and tasks time is logged against, plus read invoices and account settings. Use when the user wants to log or edit time, manage Harvest projects/clients/tasks, or check what was billed — even if they…
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
linear
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
polymarket
Query Polymarket prediction market data — search markets, get prices, orderbooks, and price history. Read-only via public REST APIs, no API key needed.