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-setupnpx skills add feO2x/guided-coding --skill guided-coding-setupgit 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.00661 |
| Opus 5 | $0.00016 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
guided-coding-setup 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 yesterday.
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
94% identical to setup — 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Guided Coding
Set up or upgrade Guided Coding in the current repository. Preserve project-specific instructions and user-authored content. Never modify existing plan or Plan Deviations documents.
1. Inspect the repository
Read the root AGENTS.md when present, ai-plans/AGENTS.md when present, nested instruction
files, build manifests, task runners, scripts, and CI configuration.
Identify feedback loops and their exact commands. Look for:
- compilers, transpilers, type checkers, static analyzers, and linters;
- unit, integration, end-to-end, coverage, and mutation tests;
- benchmarks and performance tests; and
- dependency, secret, container, and source-code security scans.
Do not invent commands or list tools merely because they are common for the detected language. Prefer the repository's documented entry points. When a command is safe, non-destructive, and reasonably bounded, run it to detect stale instructions. Do not claim that a command passed unless it was executed successfully; report why any documented command was not run. If existing Guided Coding instructions conflict with this version and resolving them would discard a project-specific decision, ask before editing.
2. Update the root instructions
Create AGENTS.md if it does not exist. Otherwise make the smallest idempotent update that
preserves unrelated sections.
Ensure it contains:
## When you implement a plan, stating that:- plans in
ai-plans/are frozen after their Planning Phase; - only acceptance criteria may change, from
- [ ]to- [x]; - a criterion is checked only after the implementation and relevant feedback loops verify it;
- unmet criteria remain unchecked and their wording is never changed; and
- material departures from explicit plan decisions require a Plan Deviations document rather than edits to the frozen plan.
- plans in
## Feedback loops, listing each repository-confirmed command and what it verifies. State plainly when no automated feedback-loop command can be confirmed.## How to write plans, linking toai-plans/AGENTS.md.## This is your spaceas the final section, inviting agents to record noteworthy repository discoveries for later discussion. Preserve any notes already in that section.
What ships with it
2 files 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.
- yesterday First seen · 66 lines · 33 tokens per session scan A 022eb2f06623
guided-coding-setup is a skill published in the GitHub repository feO2x/guided-coding (6 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 661 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to setup, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…