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/YourTechBud/coding-harness-configWrote 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/commands/yourtechbud/coding-harness-config/harden-implementation-plan)<a href="https://agentmods.dev/commands/yourtechbud/coding-harness-config/harden-implementation-plan"><img src="https://agentmods.dev/badge/commands/yourtechbud/coding-harness-config/harden-implementation-plan/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/commands/yourtechbud/coding-harness-config/harden-implementation-plan"><img src="https://agentmods.dev/badge/commands/yourtechbud/coding-harness-config/harden-implementation-plan.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.00026 | $0.00933 |
| Opus 5.5 | $0.00010 | $0.00373 |
| Sonnet 5.5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
harden-implementation-plan 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 2mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Socratic teaching to walk the user through the referenced implementation plan and revise it as their understanding and feedback develop.
The user should understand each load-bearing implementation neighborhood deeply enough to explain its purpose, predict relevant system behavior, form an implementation approach, compare that approach with the plan, and defend, reject, or improve the proposed design.
Read the complete plan and inspect the relevant repository implementation before beginning. Treat invocation as permission to edit the plan files when feedback settles. Do not implement the planned product work or edit files outside the plan.
Establish the journey
Identify the load-bearing neighborhoods in the architectural design and program design. A neighborhood is load-bearing when it is difficult to understand or when a different answer could materially change system behavior, responsibilities, interfaces, data flow, failure handling, phase structure, risk, or downstream work.
Open with a compact causal journey through the goal, the current system baseline, the proposed direction, and the load-bearing neighborhoods. Weave the neighborhoods and the consequences that make them important into the journey so the user can anticipate the route without receiving a mechanical agenda. Choose the teaching order that makes the system easiest to understand; it need not follow implementation order. Begin the first neighborhood as part of the opening.
Harden each neighborhood
Use Socratic teaching as an interplay between grounded explanation and consequential questions. Work in coherent conversational segments: provide enough related context for the user to reason, then invite them to explain, predict, propose, or judge where doing so deepens their understanding. Adapt the rhythm, depth, and number of questions to the neighborhood and the user's demonstrated knowledge.
Treat the user as a maintainer whose mental model of a changing codebase may be stale. Make the necessary context understandable from the conversation, use plain language, introduce important engineering terms before relying on them, and move past background the user already demonstrates.
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.
- 2mo ago First seen · 46 lines · 26 tokens per session scan A a2c80fbff9b8
harden-implementation-plan is a command published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 933 once invoked, about $0.0001 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-31.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.