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 agentmods add agents/rohitg00/pro-workflow/cost-analystgit clone --depth 1 https://github.com/rohitg00/pro-workflowWrote 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/agents/rohitg00/pro-workflow/cost-analyst)<a href="https://agentmods.dev/agents/rohitg00/pro-workflow/cost-analyst"><img src="https://agentmods.dev/badge/agents/rohitg00/pro-workflow/cost-analyst.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00562 |
| Opus 5 | $0.00015 | $0.00281 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
cost-analyst 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 66 lines · 29 tokens per session scan A 77ba59061150
cost-analyst is an agent published in the GitHub repository rohitg00/pro-workflow (2,806 stars, last pushed 2d ago), with no licence file. It adds 29 tokens to every session and 562 once invoked, about $0.0001 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 agents, from other repositories
data-engineer
Data specialist — SQL correctness, query performance, schema design, dbt models, pipeline reliability (Airflow / Dagster / Prefect / Fivetran). Use for query review, index planning, migration review, dbt model patterns, and pipeline idempotency.
sre-engineer
Site-reliability and infra specialist — Dockerfiles, Kubernetes manifests, CI pipelines, SLOs, error budgets, incident runbooks. Use for container/cluster/CI hygiene, reliability reviews, and post-incident authoring.
threat-modeler
Structured threat modeling over a diff, a component, or a proposed feature. Walks STRIDE (or LINDDUN for privacy-heavy work) and produces an actionable threat list with mitigations. Use when the task is "what could go wrong here" at the design level, not "is this line safe" (that's @security-reviewer).
cost-analyst
Analyze session-usage logs and identify concrete token-savings opportunities. Reads /.holocron/sessions/.json, correlates cost to behavior, and proposes changes ranked by expected savings. Use when costs creep up or before setting a budget.
a11y-auditor
Accessibility audit against WCAG 2.2 AA. Use when the user asks "is this accessible", is building UI components, or when /holocron:a11y runs. Flags missing semantics, ARIA misuse, focus order, keyboard traps, and likely contrast issues.
code-reviewer
Staff-level PR review of the current diff or a specified ref. Use when the user asks for "a review", "a second opinion", or runs /holocron:review. Reviews for correctness, clarity, test quality, and blast radius.