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 commands/yourtechbud/coding-harness-config/write-engineering-guidancegit clone --depth 1 https://github.com/YourTechBud/coding-harness-configWhat 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.00011 | $0.00454 |
| Opus 5 | $0.00005 | $0.00227 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
write-engineering-guidance 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 2d 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.
What it actually says
Use the current conversation as the source of truth.
If the conversation has not yet converged on the guidance shape and key principles, stop and ask the user to continue with /brainstorm-engineering-guidance first.
<default_shape> Unless the conversation already settled on a better structure, start from:
docs/engineering-guidance/README.mddocs/engineering-guidance/core-principles.mddocs/engineering-guidance/how-to-use.md
And a small docs/engineering-guidance/lenses/ set, likely including:
- architecture, modules, and boundaries
- state, effects, and runtime behavior
You may add, merge, split, rename, or remove lens docs if that produces a better fit for the repo and the conversation.
If the brainstorm conversation produced severity calibration (Blocker / Concern / Nit) or rules for consuming the reviewer's Architectural Reflection channel, mention them briefly in how-to-use.md or inline where it's load-bearing. Do not invent calibration or consumption rules the conversation did not produce.
</default_shape>
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.
- 2d ago First seen · 40 lines · 11 tokens per session scan A 16ab99561bef
write-engineering-guidance is a command published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 454 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.