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 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/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/arch1esun/arcgentic/execute-round"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/execute-round.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 85 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00065 | $0.01030 |
| Opus 5.5 | $0.00026 | $0.00412 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 87 lines · 65 tokens per session scan A e6c262d86c9a
execute-round is a skill published in the GitHub repository Arch1eSUN/Arcgentic (285 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.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
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
02-user-stories
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.
07-epic
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
09-defect
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.
01-ticket-info
Retrieve and display a ticket from the configured ticketing tool. Use when the user wants to see, show, or look up a ticket's details. Not for creating a ticket, or commenting on, transitioning, or reassigning one.