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 feO2x/guided-coding --skill guided-coding-setupgit clone --depth 1 https://github.com/feO2x/guided-codingWrote 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/feo2x/guided-coding/guided-coding-setup)<a href="https://agentmods.dev/skills/feo2x/guided-coding/guided-coding-setup"><img src="https://agentmods.dev/badge/skills/feo2x/guided-coding/guided-coding-setup/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/feo2x/guided-coding/guided-coding-setup"><img src="https://agentmods.dev/badge/skills/feo2x/guided-coding/guided-coding-setup.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.00033 | $0.00928 |
| Opus 5.5 | $0.00013 | $0.00371 |
| Sonnet 5.5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
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 1mo 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
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Guided Coding
Your goal is to set up or upgrade Guided Coding in the current repository. After finishing, report what you changed, give the customization tips below, and stop.
Guided Coding needs these artifacts:
AGENTS.mdat the repository root, listing the feedback loops and pointing toai-plans/AGENTS.md.ai-plans/, the folder holding all plans and Plan Deviations documents.ai-plans/AGENTS.md, describing the folder, its file naming rules, and how Frozen Plans are treated.
The outcome must be idempotent. Running this skill on a repository sets the artifacts up from scratch, brings outdated ones up to date, or leaves current ones untouched. Content unrelated to Guided Coding, such as project-specific instructions or user-authored notes, is never changed.
1. Inspect the Repository
Read the root AGENTS.md and ai-plans/AGENTS.md if they exist, plus build manifests, task runners, scripts, and CI configuration.
Identify the feedback loops and their exact commands. Look for:
- compilers, type checkers, static analyzers, and linters;
- automated tests, code coverage, and mutation testing tools;
- benchmarks; and
- dependency, secret, container, and source-code security scans.
Only select commands that are immediately executable in the repository. Do not list tools merely because they are common for the detected language.
2. Ensure the Root AGENTS.md
Create AGENTS.md in the repository root if it does not exist. Otherwise, make the smallest update that adds what is missing and corrects what is outdated. Match existing sections by meaning, not by exact heading.
Ensure it contains:
## Feedback Loops: each command and what it verifies. Report to the user when no feedback loops could be found, and warn thatguided-coding-write-planrefuses to write plans until at least one is listed.## Guided Coding: a link toai-plans/AGENTS.md, noting that it holds the file naming conventions and the rules for working with Frozen Plans. Do not restate those rules here; they live next to the plans they govern, and agents pick them up when they read the folder.
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.
- 1mo ago Changed · -2 lines 9d3c1474ee2b
- 1mo ago Changed · -2 lines a5cafd25cd3a
- 1mo ago 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 3d ago), licensed MIT. It adds 33 tokens to every session and 928 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…