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/execute-roundnpx skills add Arch1eSUN/Arcgentic --skill execute-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/execute-round)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/execute-round"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/execute-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 | $0.00065 | $0.01030 |
| Opus 5 | $0.00032 | $0.00515 |
| Sonnet 5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
execute-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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
execute-round
Orchestrates the 4-commit chain for an arcgentic round per spec § 4.2.3. Reads the planned
handoff (from plan-round skill or hand-authored), then executes Phase 1-4 via the
arcgentic Python CLI.
When to invoke
- User says "let's execute round R{N}" or "run the 4-commit chain for the handoff at ..."
- User runs
/execute-round <round_name>slash command - A handoff doc exists at
docs/superpowers/plans/...and dev work is ready to start
Prerequisites
Requires the arcgentic CLI:
- Stable:
pipx install arcgentic - Dev:
cd toolkit && pip install -e ".[dev]"
Requires a planned handoff doc — run /plan-round first if missing.
V1 projects must resolve the session-mode gate before implementation. If
project.session_mode.mode is already present in .agentic-rounds/state.yaml,
use it and do not ask again:
arcgentic session-mode recommend --round=$ROUND --handoff=$HANDOFF_PATH
arcgentic session-mode prompt --round=$ROUND --handoff=$HANDOFF_PATH --mode=multi-session --role=developer
Inputs
Parse from $ARGUMENTS:
round_name(e.g. "R10-L3-aletheia")handoff_path(defaults to most recentdocs/superpowers/plans/{date}-{round}-handoff.md)--dry-runflag (optional; skip all commits and pushes)
Workflow
When invoked:
- Verify the handoff doc exists at
handoff_path. - Shell out:
arcgentic execute-round-impl --round=$ROUND --handoff=$HANDOFF_PATH [--dry-run] - The CLI orchestrates 4 phases:
- Phase 1 — Entry-admin commit: commit handoff + state-row updates
- Phase 2 — BA design pass: dispatch ba-designer → write design doc → commit
- Phase 3 — Dev body: dispatch developer → run pre-audit quality gates (mypy / pytest / ruff) → inline CR step → inline SE step (MANDATE #20: NO BA design in SE brief) → commit
- Phase 4 — State refresh + self-audit handoff: compose self-audit handoff doc with stable artifact/fixed-anchor facts → run
arcgentic audit-check --strict-extended→ write → commit
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.
- 5d ago First seen · 87 lines · 65 tokens per session scan A e6c262d86c9a
execute-round is a skill published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 23d ago), licensed MIT. It adds 65 tokens to every session and 1,030 once invoked, about $0.0003 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
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…
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…
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…