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/feo2x/guided-coding/guided-coding-finish-plannpx skills add feO2x/guided-coding --skill guided-coding-finish-plangit clone --depth 1 https://github.com/feO2x/guided-codingWhat 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.00033 | $0.00622 |
| Opus 5 | $0.00016 | $0.00311 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
guided-coding-finish-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 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.
This is a copy
97% identical to finish-plan — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish a Plan
Finish the plan named by the user. If none is named, proceed only when exactly one uncommitted plan
draft exists in ai-plans/; otherwise ask for its path.
1. Validate
Read the repository instructions and confirm that:
- The filename is either
YYYY-MM-DD-HHMM-<issue-id>-<kebab-case-description>.mdor, without an issue,YYYY-MM-DD-HHMM-<kebab-case-description>.md. - Variable filename segments contain only lowercase ASCII letters, digits, and single hyphens, and do not start or end with a hyphen.
- The file starts with
# Title, followed by exactly## Rationale,## Acceptance Criteria, and## Technical Details, in that order. - Every acceptance criterion is an unticked task (
- [ ]). - Referenced plan documents exist, and claims about existing source files are accurate. Paths for files the plan intends to create are valid references when identified as planned work.
Report validation failures. Fix them only after the user agrees; the Planning Phase is still open until the plan is committed.
2. Commit and freeze
Inspect git status and the staged diff. Preserve unrelated working-tree and staged changes. Stage
the plan if needed, then use a path-limited commit so the commit contains only the plan file. Verify
the resulting commit's file list before continuing; if it contains anything else, stop and report
the problem without rewriting history. Follow repository commit conventions and do not push. The
successful commit ends the Planning Phase and freezes the plan.
3. Optionally publish the first plan
The first plan for a tracked issue may become that issue's description. Follow-up plans are not published there.
Use the tracker and target project documented by the repository. If neither is documented, infer them only when the git remote and tracker clearly agree, state the inferred target, and ask the user to confirm it. If the project has no tracker, skip this step.
Read the current issue title and description before asking to publish. Explain that publishing replaces the complete issue description. If it is non-empty, show or summarize what would be replaced and require explicit confirmation to overwrite it. Publish the plan body only. For GitHub:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 62 lines · 33 tokens per session scan A 5a9367108045
guided-coding-finish-plan is a skill published in the GitHub repository feO2x/guided-coding (6 stars, last pushed 19d ago), licensed MIT. It adds 33 tokens to every session and 622 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to finish-plan, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".