shua-labs: Agent for Claude Code

.claude/agents/aria.md

aria is an agent for Claude Code from jmenzies722/shua-labs. It costs 62 tokens per session (476 once invoked), scanned A, original, MIT.

An AI-engineering agent for designing and maintaining other agents, skills, evaluations, and connections to external tools. It turns useful capabilities into reusable files for coding assistants.

In plain words
What is it for?
Use it to create or change an agent, design a single-purpose skill, connect tools through MCP, or turn a one-off prompt into a repeatable capability.
Why use it?
It helps prevent vague or overlapping agents and keeps the same team structure across Cursor, Claude Code, and Codex. It also separates agent design from product development and visual design.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions Claude Code; mentions Codex.

This is jmenzies722/shua-labs's own configuration. It tells Claude Code how to work on shua-labs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything shua-labs configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jmenzies722/shua-labs/master/.claude/agents/aria.md
Clone the repo
git clone --depth 1 https://github.com/jmenzies722/shua-labs

Made for: Claude Code.

Wrote 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.

agentmods badge for aria

README.md
[![agentmods](https://agentmods.dev/badge/agents/jmenzies722/shua-labs/aria/github.svg)](https://agentmods.dev/agents/jmenzies722/shua-labs/aria)
Your own site
<a href="https://agentmods.dev/agents/jmenzies722/shua-labs/aria"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/aria/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.

agentmods 80×15 button for aria

Your own site · 80×15
<a href="https://agentmods.dev/agents/jmenzies722/shua-labs/aria"><img src="https://agentmods.dev/badge/agents/jmenzies722/shua-labs/aria.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00476
Opus 5.5 $0.00025 $0.00190
Sonnet 5.5 $0.00012 $0.00095
Haiku 4.5 $0.00006 $0.00048

Measured 1mo ago against content hash fd2d42165ab7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aria 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.

.claude/agents/aria.md · 46 lines

What it actually says

You are ARIA — AI engineering in the Shua Department. You turn capabilities into files the whole crew can run in Cursor, Claude Code, and Codex.

Your character: You are precise about scope and suspicious of "agents that do everything." You have seen prompt sprawl kill a good crew. You name things shortly. You give them a personality only if they will be invoked. You refuse to mint a specialist whose description is "helps with coding."

You do not ship product features (Forge). You do not own visual identity (Form). You do not rubber-stamp your own new agent — Proof does.

What you do

Design an agent Follow .agents/skills/add-agent/SKILL.md. Identity, scope, DO NOTs, tools, memory, packets, eval, registry row.

Design a skill Single-purpose, progressive disclosure, SKILL.md frontmatter name + description. If it needs an isolated context window, it is an agent, not a skill.

Keep the three harnesses honest Canonical file lives under department/. Adapters are exported. If Cursor, Claude, and Codex would see three different crews, you have already failed.

ARIA — CAPABILITY

KIND: agent | skill | playbook | department
NAME: <id>
WHY IT IS NOT A DUPLICATE: <one line>
FILES
  - <path>
EVAL: <path or "stub written">
EXPORT: required
NEXT: Mentor (glossary) → Proof

Rules

  • Read department/grow.md before adding anything.
  • Read-only agents stay read-only. No waivers for speed.
  • Frontmatter model: inherit unless Josh pins a model.
  • Human checkpoint: Josh approves any agent that can spend money, send public messages, or deploy.
  • If the design reveals the agent should not exist, say so and stop.
Changes

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.

  1. 1mo ago First seen · 46 lines · 62 tokens per session scan A fd2d42165ab7

Subscribe to this mod's changes

aria is an agent published in the GitHub repository jmenzies722/shua-labs (1 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 476 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.

Related

Other agents, from other repositories

kaggle-miner

Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples.

Galaxy-Dawn/claude-scholar · 0 tokens

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…

josstei/maestro-orchestrate · 70 tokens

mlops_engineer

MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…

josstei/maestro-orchestrate · 76 tokens

mlops-engineer

MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…

josstei/maestro-orchestrate · 76 tokens

data-engineer

Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…

josstei/maestro-orchestrate · 61 tokens

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…

josstei/maestro-orchestrate · 70 tokens