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 close-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/close-round)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/close-round"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/close-round.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00375 |
| Opus 5 | $0.00026 | $0.00187 |
| Sonnet 5 | $0.00010 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
close-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 8d 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
close-round
Closes an arcgentic round after external audit PASS. This is an orchestrator-owned closeout seam, not a developer or auditor task.
Preconditions
.agentic-rounds/state.yamlhascurrent_round.state: passed.current_round.audit_verdict.outcomeisPASS.current_round.audit_verdict.commitis set to the audit commit.- The verdict file exists and passes both:
arcgentic verdict-completeness <verdict.md>arcgentic audit-check <verdict.md> --strict --strict-extended
Command
arcgentic close-round \
--state-file .agentic-rounds/state.yaml \
--verdict <docs/audits/round-verdict.md> \
--audit-commit <audit-commit-sha>
Outputs
current_round.statebecomesclosed.current_round.state_historygains aclosedentry.last_passed_roundrecords round id, audit commit, verdict doc, and close time.- The command prints a next-round recommendation for the orchestrator.
Boundaries
- Do not run before external audit PASS.
- Do not write, edit, or replace the external audit verdict.
- Do not use close-round to resolve NEEDS_FIX or AUDIT_INCOMPLETE.
- Do not perform release tagging, publishing, or next-round planning unless the user explicitly starts that separate orchestrator step.
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.
- 8d ago First seen · 43 lines · 51 tokens per session scan A 5101716feee1
close-round is a skill published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 375 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…
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…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
debt-ops-review
Audit the tech-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 check the debt registry. Stale entries drop with "drop A,B,C".
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…