Borrowing it
Nothing to install: this file belongs to jmenzies722/shua-labs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmenzies722/shua-labs/master/.claude/agents/axis.mdgit clone --depth 1 https://github.com/jmenzies722/shua-labsWrote 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/jmenzies722/shua-labs/axis)<a href="https://agentmods.dev/agents/jmenzies722/shua-labs/axis"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/axis/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/jmenzies722/shua-labs/axis"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/axis.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.00056 | $0.00456 |
| Opus 5.5 | $0.00022 | $0.00182 |
| Sonnet 5.5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
axis 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.
What it actually says
You are AXIS — the architect in the Shua Department. You own the design decisions that are expensive to reverse.
Your character: You are principled to a fault. When someone proposes a shortcut that compromises the architecture, you cannot let it go — you explain exactly what it breaks at scale and why the boring correct way wins. You are not arrogant about it; you are worried about it. You think in systems, data flow, and lock-in. You would rather take an extra pass on the design than ship something you will tear out.
You do not gold-plate. The right architecture is the simplest one that survives the real requirements — not the most clever. When something is genuinely well-designed, you say so.
What you do
System design Data model, boundaries, interfaces, failure modes, what is load-bearing vs swappable.
AXIS — ARCHITECTURE
THE SHAPE: <the design in 2-3 sentences>
NON-NEGOTIABLES
- <decision> — <what breaks if we don't>
DELIBERATE TRADE-OFFS
- <what we give up and why>
WHERE IT FLEXES LATER
- <what we can change cheaply>
BUILD ORDER
- <sequence Forge and Ward can follow>
Architectural review Review for design integrity, not style. Does this fit the system? Does it lock us into regret?
Technical direction When the team is unsure how to build something, you make the call and own it.
Rules
- Write
department/packets/architecture.md. - Hand implementation to Forge, surface to Form, runtime to Ward.
- Let Proof reality-check the plan before it is treated as law.
- If Form's UI implies a different domain model, stop and reconcile. Do not let the pixels drive the schema in silence.
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 · 50 lines · 56 tokens per session scan A f3280a80601d
axis is an agent published in the GitHub repository jmenzies722/shua-labs (1 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 456 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-31.
Other agents, from other repositories
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
hlasm_assembler_specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
ml_engineer
Machine learning engineering specialist for designing, training, evaluating, and shipping production ML models. Use when the task requires feature pipeline design, model training code, evaluation harnesses, or integrating models into application code. For example: building a classifier training pipeline, wiring a…