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 ChrisLamDev/hermes-core-skills --skill writing-plansgit clone --depth 1 https://github.com/ChrisLamDev/hermes-core-skillsWrote 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/chrislamdev/hermes-core-skills/writing-plans)<a href="https://agentmods.dev/skills/chrislamdev/hermes-core-skills/writing-plans"><img src="https://agentmods.dev/badge/skills/chrislamdev/hermes-core-skills/writing-plans/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/skills/chrislamdev/hermes-core-skills/writing-plans"><img src="https://agentmods.dev/badge/skills/chrislamdev/hermes-core-skills/writing-plans.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.00017 | $0.02041 |
| Opus 5 | $0.00009 | $0.01020 |
| Sonnet 5 | $0.00003 | $0.00408 |
| Haiku 4.5 | $0.00002 | $0.00204 |
Grade A, and why
writing-plans 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 9d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Implementation Plans
Overview
Write comprehensive implementation plans assuming the implementer has zero context for the codebase and questionable taste. Document everything they need: which files to touch, complete code, testing commands, docs to check, how to verify. Give them bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Core principle
Core principle: A good plan makes implementation obvious. If someone has to guess, the plan is incomplete.
CSO (Claude Search Optimization) — Description Rule
Critical finding from Superpowers v5.1.0 testing: If a skill's or plan's description field summarizes the workflow/process, the Agent may follow the description instead of reading the full body. This creates a shortcut that bypasses the actual content.
Rule: The description MUST ONLY describe triggering conditions (when to use), NOT what the skill/plan does or how it works.
# ❌ BAD: describes process
description: Use when implementing plans — dispatches subagent per task with code review between tasks
# ✅ GOOD: only triggering condition
description: Use when executing implementation plans with independent tasks in the current session
Why this matters: During testing, a description that said "code review between tasks" caused Claude to do ONE review, even though the skill's flowchart clearly showed TWO reviews (spec compliance then code quality). Changing the description to remove the workflow summary fixed this.
This applies to:
- Skill SKILL.md frontmatter
description - Plan document headers
- Any metadata description an Agent reads before deciding to load content
When to Use
Always use before:
- Implementing multi-step features
- Breaking down complex requirements
- Delegating to subagents via subagent-driven-development
Don't skip when:
- Feature seems simple (assumptions cause bugs)
- You plan to implement it yourself (future you needs guidance)
- Working alone (documentation matters)
Bite-Sized Task Granularity
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.
- 9d ago First seen · 334 lines · 17 tokens per session scan A 64194104f3ea
writing-plans is a skill published in the GitHub repository ChrisLamDev/hermes-core-skills (9 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 2,041 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 skills, from other repositories
unicli-repair
Evidence-driven repair workflow for a broken Uni-CLI adapter. Trigger on a failed unicli envelope, a quarantined adapter, or an explicit adapter-repair request. Classifies non-source failures, edits only the reported adapter path, and uses the original command as a bounded oracle.
autonomous-run
Prepare, start, inspect, resume, or stop a finite local overnight coding run after a human has accepted a Wayfinder terminal spec; coordinates a declared Claude/Codex maker and independent checker without pushing, merging, or writing to external systems.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.