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/polish-beadsnpx skills add hoangsonww/Forge-Agentic-Coding-CLI --skill polish-beadsgit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWrote 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/hoangsonww/forge-agentic-coding-cli/polish-beads)<a href="https://agentmods.dev/skills/hoangsonww/forge-agentic-coding-cli/polish-beads"><img src="https://agentmods.dev/badge/skills/hoangsonww/forge-agentic-coding-cli/polish-beads.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00239 |
| Opus 5 | $0.00020 | $0.00120 |
| Sonnet 5 | $0.00008 | $0.00048 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
polish-beads 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 4d 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
Use the verbatim prompt at .flywheel/prompts/polish-beads.md.
Each round, verify:
- Self-containment — a fresh agent can execute without the plan.
- Dependencies —
depends_onis correct; no missing edges. - Tests — concrete obligations with logging expectations.
- Coverage — cross-reference vs
.flywheel/plans/*.md. - Duplicates — merge overlapping beads (see
dedupe-beadsprompt). - Forge invariants — permission gate,
LEGAL_TRANSITIONS, UI < 120KB, provider probe ~1.5s.
Stop when two consecutive rounds produce only small corrective
edits. If polishing has flatlined after 3 rounds, switch to a fresh
session and .flywheel/prompts/fresh-eyes.md.
Final round: run through a different model (e.g. switch Claude ↔ Codex). Different models catch different things.
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.
- 4d ago First seen · 24 lines · 41 tokens per session scan A 3e47c083a429
polish-beads is a skill published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 239 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
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
raise-issue
Turns "this is broken" into a well-formed issue in the team's tracker, written in the codebase's own vocabulary. Built for someone who uses the product and does not read code — it asks a few plain-English questions, works out for itself which part of the code they are describing, checks whether the same thing has…
trello-handoff
Move the current Trello card through the configured Symphony-for-Trello lifecycle. Use when picking up work, handing off for human review, marking a blocker, or completing a merge.
trello-workpad
Maintain the single Codex workpad comment on the current Trello card. Use during implementation, retry, rework, review handoff, blocked handoff, or merge handoff.
tendrillable
Find "Tendrillable" GitHub issues — open, recent, code-requiring issues that an agent can plan and one-shot WITHOUT asking clarifying questions, with high probability of success. Classifies a repo's open issues against the Tendrillable rubric and prints a ranked list of issue URLs. Use when asked to find tendrillable…