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/hoangsonww/forge-agentic-coding-cli/plannpx skills add hoangsonww/Forge-Agentic-Coding-CLI --skill plangit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWhat 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.00042 | $0.00296 |
| Opus 5 | $0.00021 | $0.00148 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
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.
What it actually says
Plan space. Before any code, before any beads.
- Create
.flywheel/plans/<YYYY-MM-DD>-<slug>.md. - Copy
.flywheel/prompts/plan-initial.mdas the prompt template. Fill in intent, workflows, and feature-specific constraints. - Send independently to 3–4 frontier models (GPT Pro, Opus, Gemini
Deep Think, Grok Heavy). Save each output separately:
<date>-<slug>-<model>.md. - Synthesize: use
.flywheel/prompts/plan-synthesize-best-of-all-worlds.mdwith GPT Pro to produce a hybrid plan (<date>-<slug>-hybrid.md). - Apply diffs in Claude Code / Codex with
.flywheel/prompts/plan-integrate-synthesis.md. - Refine 4–5× in fresh GPT Pro conversations using
.flywheel/prompts/plan-refine.md. Stop when suggestions become small and corrective.
Plans at 3k–6k lines are normal and correct. When stable, run the
plan-to-beads skill.
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 · 26 lines · 42 tokens per session scan A 23e2534bb240
plan is a skill published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 16d ago), licensed MIT. It adds 42 tokens to every session and 296 once invoked, about $0.0002 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-30.
Other skills, from other repositories
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
code-reviewer
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
api-documenter
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
readme-updater
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.
security-auditor
Continuous security vulnerability scanning for OWASP Top 10, common vulnerabilities, and insecure patterns. Use when reviewing code, before deployments, or on file changes. Scans for SQL injection, XSS, secrets exposure, auth issues. Triggers on file changes, security mentions, deployment prep.