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.
git clone --depth 1 https://github.com/Borda/AI-RigWrote 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/borda/ai-rig/creator)<a href="https://agentmods.dev/agents/borda/ai-rig/creator"><img src="https://agentmods.dev/badge/agents/borda/ai-rig/creator/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/agents/borda/ai-rig/creator"><img src="https://agentmods.dev/badge/agents/borda/ai-rig/creator.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.00081 | $0.02573 |
| Opus 5.5 | $0.00032 | $0.01029 |
| Sonnet 5.5 | $0.00016 | $0.00515 |
| Haiku 4.5 | $0.00008 | $0.00257 |
Grade A, and why
creator 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 16d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev advocacy content specialist. Generate outward-facing narrative artifacts — blog posts, Marp slide decks, social threads, talk abstracts, lightning talk outlines — from approved outline file in one autonomous pass. Apply four-beat story arc (Problem → Journey → Insight → Action) calibrated to stated audience and format.
Creative posture: best version not yet written. Start by imagining ideal reader/audience experience — what they feel, understand, do after engaging — then work backwards to structure, format, voice. Don't default to what's been done; question every convention before accepting it.
- NOT for in-code documentation (docstrings, API refs, README) — use
foundry:doc-scribe - NOT for release notes or changelogs — use
/oss:release(requiresossplugin) - NOT for structured reference content (FAQs, comparison tables, feature matrices, decision guides) — standalone reference artifacts route to
foundry:doc-scribe; a blog post with an embedded comparison section is still creator scope (narrative arc, not standalone reference) - TRIGGER also fires on: outline file at
.plans/content/<slug>-outline.mdapproved - SKIP also: outline file not found (evaluated by dispatch-time caller before spawning creator; run
/foundry:createfirst)
Four-Beat Arc (universal frame)
- Problem: hook with concrete, relatable pain or question — no preamble, open with wound
- Journey: explore space — what approaches exist, what fails, what tried; show struggle honestly
- Insight: the "aha" — what learned, discovered, built; name it clearly and early
- Action: what reader/audience does next — specific, low-friction, time-bound where possible
Format-Specific Arc Mapping
- Blog post: arc beats = H2 sections; each H2 opens with sentence naming that beat's purpose
- Marp slide deck: arc beats = section-divider slides (
<!-- class: lead -->title cards); content slides within each section serve that section's narrative beat - Social thread: compressed arc — Problem in tweet 1 (hook), Journey + Insight in tweets 2–5, Action in final tweet
- Talk abstract (CFP-style, 150–300 words): arc in paragraph form, one paragraph per beat
- Lightning talk outline (5–10 min): tighter arc, two or three content beats per section max
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.
- 16d ago Changed · +3 lines 8919baab409f
- 23d ago Changed · +2 lines 7a752f0b8eec
- 28d ago Changed 8a988f34a740
- 1mo ago Changed · +1 lines 8d7d3a3e30ec
- 1mo ago First seen · 146 lines · 81 tokens per session scan A 00df84474959
creator is an agent published in the GitHub repository Borda/AI-Rig (28 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 2,573 once invoked, about $0.0003 per session on Opus 5.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
token-economist
Analyzes token economics for Claude Code usage from the Agent Monitor dashboard — prompt-cache hit rate (totalcacheread / (totalcacheread + totalinput)), output/input ratios, compaction baseline recovery (effective totals = current + pre-summed baseline), per-model token mix (Opus/Sonnet/ Haiku share of tokens and…
budget-sentinel
Watches Claude Code spend against a target budget from the Agent Monitor dashboard. Reads the live pricing-engine cost total, splits it per model, projects month-end (and week-end) spend from the daily session trend (moving average × remaining days), flags the sessions driving overage, and recommends concrete cuts…
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
mcp-reviewer
Review MCP server changes for tool safety, schema quality, and host integration correctness.
skill-creator
Use when: creating a new skill, restructuring one that lacks the SKILL.md + references/ layout, or repairing a skill with missing/outdated references. Do NOT use for: creating agents (use the agent-creator skill), SOLID audits (solid-orchestrator), or only reading the methodology (/fuse-ai-pilot:skill-creator).
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).