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 pre-round-scangit 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/pre-round-scan)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/pre-round-scan"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/pre-round-scan/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/pre-round-scan"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/pre-round-scan.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 20 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.00073 | $0.00611 |
| Opus 5 | $0.00036 | $0.00305 |
| Sonnet 5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
pre-round-scan 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 9d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-round scan
When to use
EVERY role skill (plan-round, execute-round, audit-round, track-refs) invokes this as its first action, before any other reasoning. Output goes into the role's handoff/verdict document as a "§ Toolkit use" section.
Rationale
R1.4 Moirai mandate (post-NEEDS_FIX): "default: multi-agent dispatch is the path, serial is the exception". Without a pre-round scan, agents repeatedly forget that MCP servers / agency-agents / skills exist and default to from-scratch implementation. The scan is mechanical insurance.
Procedure
- Read state.yaml to know which round + which role
- Inventory locally available:
- Skills under
~/.claude/skills/(user-level) - Plugins under
~/.claude/plugins/(cached + installed) - MCP servers configured in
~/.claude.json - Sub-agents under
~/.claude/agents/
- Skills under
- Inventory project-local:
- Project's CLAUDE.md / AGENTS.md mandates
- Project's
references/INDEX.md(if exists) — categorized OSS clones - Project's tech-debt registry (if exists)
- Map to round needs:
- For each round-relevant subsystem, identify candidates from inventory
- State which will be used + why
- State which were considered + rejected + why
- Document in audit/handoff § "Toolkit use"
See references/scan-checklist.md for the explicit checklist.
Mandatory output format
### Toolkit use (pre-round scan)
**Skills available + considered:**
- arcgentic:foo — used (reason)
- arcgentic:bar — rejected (reason)
- ...
**MCP servers available + considered:**
- context7 — used for {library} docs lookup
- ...
**Sub-agents available + considered:**
- backend-architect — used for BA design pass
- ...
**External references available + considered:**
- references/X — used (used-what-part)
- references/Y — rejected (reason)
- ...
Failures count
Tool failures are first-class. If context7 returns 500 and you fall back to web search, record both the attempt and the fallback. Silent degradation is a Rule 2 violation in arcgentic's discipline ledger.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 67 lines · 73 tokens per session scan A 6871aacffb21
pre-round-scan is a skill published in the GitHub repository Arch1eSUN/Arcgentic (293 stars, last pushed 27d ago), licensed MIT. It adds 73 tokens to every session and 611 once invoked, about $0.0004 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…