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 rchase999/aidd --skill craft-bargit clone --depth 1 https://github.com/rchase999/aiddWrote 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/rchase999/aidd/craft-bar)<a href="https://agentmods.dev/skills/rchase999/aidd/craft-bar"><img src="https://agentmods.dev/badge/skills/rchase999/aidd/craft-bar.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.1 | $0.00065 | $0.01810 |
| Opus 5 | $0.00032 | $0.00905 |
| Sonnet 5 | $0.00013 | $0.00362 |
| Haiku 4.5 | $0.00006 | $0.00181 |
Grade A, and why
craft-bar 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 6d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The craft bar
The contract says what to build. This says how well. It applies to every project, in every domain.
The rule
Use the strongest thing the domain actually offers. Not the first thing that works, not the easiest thing to type, not the answer you happen to remember from 2019. If the ecosystem has a better primitive than the obvious one, use it — and say why in the charter.
It cuts both ways. The strongest tool for a log parser is a tight state machine and good tests, not a framework. Reaching for something heavy where something small is correct is the same failure as reaching for something crude where something powerful is correct.
Know what excellent looks like in this specific domain, then aim there. Every domain has a version of "obviously made by someone who didn't care" and a version of "someone who knew what they were doing". You are aiming at the second one, and it looks different in every domain.
Two rules that hold everywhere
1. Default-looking output is a failure mode. Every domain has a recognisable "generated by a model that didn't look at the problem" signature. If you can't tell whether a person or a model made your output, you haven't cleared the bar.
2. No borrowed filler. Nothing placeholder, nothing lorem, nothing hotlinked, nothing stock. Content, data, and assets are either real or generated by you for this project. This is deliberate: filler is how work announces that nobody looked at it.
Worked examples
These are examples of the rule, not the rule. Find the equivalent for whatever you are actually building — most projects are not web projects, and a project may span several of these.
Example: anything with a visual surface (web, landing pages, dashboards, rendered artifacts)
The tells of default output — centred hero over a purple-to-blue gradient, three equal feature cards, Inter at three weights, rounded-2xl and shadow-lg on everything, emoji as icons, evenly spaced sections with identical padding, one accent colour that means nothing.
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.
- 6d ago First seen · 103 lines · 65 tokens per session scan A 603817147267
craft-bar is a skill published in the GitHub repository rchase999/aidd (2 stars, last pushed 28d ago), licensed MIT. It adds 65 tokens to every session and 1,810 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
agentic-workflow-audit
A read-only review method for checking whether an AI-agent or language-model workflow is genuinely split into small, independent tasks with clear rules and checks.
triage-mode
Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
citation-receipts
Systematic per-citation verification protocol for academic writing. MUST be used whenever writing content that cites sources — papers, blog posts, SOTAs, or any document making factual claims about external work. Triggers (FR + EN) on any writing task involving references, citations, or bibliographic claims, or when…
sota-writer
Write structured State-of-the-Art (SOTA) reviews / literature reviews for academic research projects with zero hallucinated citations. Activate this skill whenever the user wants to write, update, or expand a SOTA. Triggers (FR + EN) : "écris un SOTA", "état de l'art sur", "revue de littérature", "mise à jour SOTA"…
general-mode
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut command.