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 skills/yourtechbud/coding-harness-config/harden-implementation-plannpx skills add YourTechBud/coding-harness-config --skill harden-implementation-plangit 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/skills/yourtechbud/coding-harness-config/harden-implementation-plan)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/harden-implementation-plan"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/harden-implementation-plan.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.00032 | $0.00949 |
| Opus 5 | $0.00016 | $0.00475 |
| Sonnet 5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 4d 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 — 48 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.
- 4d ago First seen · 48 lines · 32 tokens per session scan A 0a48d35696c2
harden-implementation-plan is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 32 tokens to every session and 949 once invoked, about $0.0002 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.