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/arch1esun/arcgentic/plan-roundnpx skills add Arch1eSUN/Arcgentic --skill plan-roundgit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/plan-round)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/plan-round"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/plan-round.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.1 | $0.00046 | $0.01027 |
| Opus 5 | $0.00023 | $0.00513 |
| Sonnet 5 | $0.00009 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
plan-round 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-round
Generates a round handoff at docs/superpowers/plans/{YYYY-MM-DD}-{round_name}-handoff.md by
dispatching the planner sub-agent with a self-contained brief, then validating its output
against the corresponding handoff template (18 / 12 / 10 section).
When to invoke
- User says "let's plan R{N}" or "create handoff for R{N}"
- User runs
/plan-roundslash-command - A new round-name appears in conversation without a corresponding handoff doc
Prerequisites
Requires the arcgentic CLI installed (the Python toolkit):
- Stable:
pipx install arcgentic(post-v0.2.0 PyPI release) - Dev (in this repo):
cd toolkit && pip install -e ".[dev]"
The CLI runs in a subprocess; this markdown skill is the thin shim that invokes it.
For V1 rounds with external workflow inputs, first validate source/spec context:
arcgentic source-intake validate docs/source-intake/*.yaml
arcgentic capability-registry build <marketplace-catalog.json>
arcgentic spec-governance status <change-dir>
For projects with project.session_mode already set, include the inherited mode
and dispatch order in the handoff instead of asking again:
arcgentic orchestrator-dispatch \
--round <round_name> \
--handoff <handoff-path> \
--mode <single-session|multi-session>
Inputs
Parse from $ARGUMENTS (passed by Claude Code):
round_name— e.g. "R10-L3-aletheia" or "R1.6.1"round_type— one of: substrate-touching | fix-round | entry-admin | close-admin | meta-admin-sweepprior_round_anchor— full 40-char SHA of prior round's last commitscope_description— optional 1-3 sentence scope (can be filled later in handoff)
If any required input is missing, ASK the user before proceeding.
Workflow
When invoked with all inputs:
-
Validate
round_namematches the patternR<phase>[.<round>[.<fix>]]orR<phase>-<name>. -
Validate
prior_round_anchoris a full 40-character hex SHA (NOT short). -
Shell out to the CLI:
arcgentic plan-round-impl \ --round=<round_name> \ --type=<round_type> \ --anchor=<prior_round_anchor> \ --scope=<scope_description>
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.
- 6d ago First seen · 101 lines · 46 tokens per session scan A f66318d5e3eb
plan-round is a skill published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 24d ago), licensed MIT. It adds 46 tokens to every session and 1,027 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
init
Write or refresh the ## Tech debt operations section in CLAUDE.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoked explicitly via /debt-ops:init (solo users get the same content from the…
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
metrics
Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes /debt-ops:metrics. Read-only, never writes the log.
review
Audit the debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or invokes /debt-ops:review. Stale entries drop with drop A,B,C.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…