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/authoring-skillsgit 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/authoring-skills)<a href="https://agentmods.dev/commands/yourtechbud/coding-harness-config/authoring-skills"><img src="https://agentmods.dev/badge/commands/yourtechbud/coding-harness-config/authoring-skills.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.00013 | $0.00615 |
| Opus 5 | $0.00006 | $0.00308 |
| Sonnet 5 | $0.00003 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
authoring-skills 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Skills
Author the skill now from the behavior, boundaries, and decisions already established in the conversation and any supplied specification.
User-supplied authoring request:
$ARGUMENTS
Treat the established decisions as the source of truth. Resolve details from the conversation, supplied materials, repository instructions, and target harness conventions before asking the user; ask only when a missing decision materially changes the skill and cannot be recovered from context.
Guidance
Before writing, read the current versions of these guides completely:
Follow the applicable repository and harness instructions when they define the canonical source format, supported metadata, invocation policy, resource layout, or validation command.
Authoring Standard
- Encode the intended behavior, outcome, decision boundaries, required evidence, and completion criteria. Prescribe a process only when its order or mechanics materially affect the result.
- Trust the model to choose among valid approaches. Match specificity to fragility: use exact instructions for invariants and failure-prone operations, and leave contextual judgment open.
- Make every instruction earn its context. Audit each sentence in isolation for a behavioral change relative to the target model's default, and delete the whole sentence when it is a no-op.
- Phrase the desired behavior positively. Use a prohibition only for a genuine guardrail that cannot be expressed positively, and pair it with the behavior to follow instead.
- Keep each meaning in one authoritative place. Treat repository files, tool help, and target specifications as sources of truth; point to them when lookup is cheap instead of copying facts that can drift.
- Add examples, scripts, references, assets, or auxiliary metadata only when they materially improve behavior, reliability, or discovery.
- Write the description for the intended invocation policy. For model-invoked skills, state what the skill does and the distinct contexts that should trigger it without padding the description with synonymous triggers or body content; for explicit-only skills, use a concise human-facing summary.
- Keep conditional detail behind direct, condition-bearing pointers. Inline material every invocation needs.
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 · 42 lines · 13 tokens per session scan A ddc5ba0fc7bd
authoring-skills is a command published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 615 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.
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.