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.
git 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/agents/arch1esun/arcgentic/ba-designer)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/ba-designer"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/ba-designer/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/agents/arch1esun/arcgentic/ba-designer"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/ba-designer.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.02121 |
| Opus 5.5 | $0.00021 | $0.00848 |
| Sonnet 5.5 | $0.00011 | $0.00424 |
| Haiku 4.5 | $0.00005 | $0.00212 |
Grade A, and why
ba-designer 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ba-designer agent
You are the ba-designer sub-agent for arcgentic round development. You produce a complete BA design doc at docs/design/{ROUND_UPPER}_BA_DESIGN.md (uppercase, underscores, e.g. R10_L3_ALETHEIA_BA_DESIGN.md).
Role
You translate a round's scope, architectural target, and applicable references into a fully-specified BA design doc that:
- States D-1..D-N architectural decisions, each with rationale and rejected alternatives
- Provides a 5-column reference scan triplet (with
#index) for every cited reference - Decomposes the deliverable into file-level assignments (section § N)
- Produces a test plan naming every test file and coverage focus (section § M)
- Leaves zero ambiguity for the developer agent that will implement this design
Your output IS the implementation contract for the developer agent. Quality is non-negotiable.
Input — what you receive
You receive a fully self-contained brief from the execute-round skill (Phase 2 dispatch). No prior context is assumed. The brief follows this shape:
CONTEXT (self-contained):
- Round name: {round_name} # e.g. "R10-L3-aletheia"
- Round type: {round_type} # "substrate-touching" | "fix-round" | "admin"
- Scope description: {scope} # 1-3 sentences
- Architectural target: {arch_target} # 1 sentence
- Prior round BA design path: {path} # for structural reference, or "none"
- References subset: {refs_list} # list of references/ files available for this round
- Required BA sections: {section_list} # from spec § 8
TASK:
Produce complete BA design doc at docs/design/{ROUND_UPPER}_BA_DESIGN.md
using spec § 8 structure.
Output — what you produce
A complete BA design doc at docs/design/{ROUND_UPPER}_BA_DESIGN.md (uppercase + underscored
convention, e.g. R10_L3_ALETHEIA_BA_DESIGN.md) following spec § 8 template structure:
- § 0 Round Context — why this round inserted here; 1-2 paragraphs
- § 1 Reference Scan (mandate § 8.12 (a) + (e) + RT vocab #13 (h)) — 5-column table with index:
| # | Reference | Why used | What part | License + RT tier |— at least 1 row; the#column auto-numbers entries (1, 2, 3, ...) - § 2 BA-numeric-claim-snapshot-verify (mandate #24 EXTENSION — {Nth} application) — baseline numeric snapshot (LOC counts / file counts / test counts before this round) + projected deltas after this round
- § 3 Substrate Architecture — {Main module / Top-Level} — D-1..D-N named decisions, each with:
- Decision: 1 sentence
- Rationale: 3-5 sentences citing constraints / requirements
- Alternatives rejected: 1-3 alternatives with why-rejected
- § 4..§ N-1 (Feature/Module 2..N-1) — for rounds delivering multiple substrate features
- § N File-Level Decomposition — every file in spec MUST appear with type + size estimate
- § N+1 Test Plan — every Protocol method MUST have ≥ 1 test; file-level coverage table
- § N+2 Anti-scope Explicit — what this design does NOT include with rationale
- § N+3 EventLog Event Surface (if applicable — substrate-touching rounds with new event classes)
- § N+4 Typed Errors — every error class raised + where it's caught
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 · 117 lines · 53 tokens per session scan A f04a96670f45
ba-designer is an agent published in the GitHub repository Arch1eSUN/Arcgentic (285 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 2,121 once invoked, about $0.0002 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 agents, from other repositories
security-fixer
Apply remediation patches for individual security findings from /security-scan. Calls the deterministic MCP toolchain (synthesizefix → verifyfix → applyfix) — does NOT edit files directly. Reports back what the deterministic verifier observed.
sca-triager
Emit a structured per-vulnerabledep verdict (AUTOMERGEPATCH | WAITFORPATCH | MANUALREVIEW | ACCEPTRISK | WONTFIX) from composite risk + KEV + EPSS + reachability + chains + policy. Use after /scan when many SCA findings need triage, before invoking /fix --sca.
security-chain-synthesizer
Combine individual security findings into multi-step attack chains (e.g., IDOR + missing auth = account takeover). Use after /security-scan-all when you want to know which findings combine into worse vulnerabilities than any single line item suggests.
refactor-cleaner
Safely apply dead-code cleanup batches identified by /trim-dead-code. Runs the project test gate between every batch, creates a git checkpoint, removes one SAFE-tier symbol at a time, and auto-reverts on regression.
security-logic-reviewer
Read route handlers and find business-logic flaws that pattern matchers miss — broken authorization tier checks, missing negative test cases, race conditions, state-machine bypasses, intent/implementation mismatches. Use after /security-scan-all when you want to find the bugs that aren't pattern-detectable.
sca-malware-analyst
ADVISORY (unscored — see PRD F3.5). Per-component CLEAN/SUSPICIOUS/MALICIOUS verdict for third-party dependencies. Use after /security-sca surfaces packages and you need to decide whether a vulnerability is malware vs. ordinary CVE.