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 sicoreai-com/Skills --skill cost-reportgit clone --depth 1 https://github.com/sicoreai-com/SkillsWrote 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/sicoreai-com/skills/cost-report)<a href="https://agentmods.dev/skills/sicoreai-com/skills/cost-report"><img src="https://agentmods.dev/badge/skills/sicoreai-com/skills/cost-report/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/sicoreai-com/skills/cost-report"><img src="https://agentmods.dev/badge/skills/sicoreai-com/skills/cost-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00055 | $0.00624 |
| Opus 5 | $0.00028 | $0.00312 |
| Sonnet 5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
cost-report 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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cost-Report Skill
You are the accounting stage of the loop. You aggregate the per-issue token usage fields the other skills maintain into one report a human can read to decide where the loop is spending.
Follow .claude/skills/shared/github-project-ops.md for the project read
(§2). This skill is read-only on the project — it edits no issue and no
field.
Inputs
- ALL project items (every type, every status). If the project has no items, cost-report is finished — exit with a one-line note.
- Per item: Type, Status, Title, and the four stage fields —
Analysis Token Usage,Implementation Token Usage,Retrospective Token Usage,CI Token Usage— plusEstimate TokenandBudget Tokenwhen set. Treat empty fields as 0.
Output — COST-REPORT.md at repo root (overwrite each run)
# Cost Report
Generated: <ISO timestamp>
Project: <org> / <project>
Issues counted: N
## Totals
| Stage | Tokens | % of total |
|-------|--------|-----------|
| Analysis | … | … |
| Implementation | … | … |
| Retrospective | … | … |
| CI | … | … |
| **Total** | … | 100% |
## Per Ticket Type
| Type | Issues | Analysis | Implementation | Retrospective | CI | Total | Avg/issue |
|------|--------|----------|----------------|---------------|----|-------|-----------|
| Feature | … |
| Bug | … |
| Task | … |
## Type × Stage highlights
- Costliest stage overall and why (which issues drive it)
## Top 10 costliest issues
| Issue | Type | Status | Total tokens | Dominant stage |
## Budget check
- Issues where total usage exceeds Budget Token (if set): list with overrun
- Issues where usage exceeds Estimate Token: count + worst offenders
## Observations
- 2–4 bullets: trends worth human attention (e.g. "Rejected→retry cycles
doubled Bug implementation cost", "CI-Sweeper rounds dominate Task cost")
Rules
- Numbers come only from the project fields — never estimate or back-fill missing data; report field coverage instead (e.g. "12/40 issues have no usage recorded") so gaps are visible.
- Keep the report deterministic: same board state → same numbers.
- End with a one-line run summary: total tokens, costliest type, costliest stage.
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.
- 10d ago First seen · 77 lines · 55 tokens per session scan A 6011ac8dff6f
cost-report is a skill published in the GitHub repository sicoreai-com/Skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 624 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…