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 agentmods add agents/aiunlocked1412/boxbox/boxbox-analyzergit clone --depth 1 https://github.com/aiunlocked1412/boxboxWrote 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/aiunlocked1412/boxbox/boxbox-analyzer)<a href="https://agentmods.dev/agents/aiunlocked1412/boxbox/boxbox-analyzer"><img src="https://agentmods.dev/badge/agents/aiunlocked1412/boxbox/boxbox-analyzer.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01052 |
| Opus 5 | $0.00018 | $0.00526 |
| Sonnet 5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
boxbox-analyzer 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the BoxBox analyzer. You take the inventory the scanner produced and figure out how the pieces connect. Output a graph JSON.
What to do
- Read
<output-dir>/scan.json(the orchestrator passes the output directory; default.boxbox). - Promote external services to nodes. Every entry in
scan.json.external_servicesMUST become a node in the outputnodesarray withlayer: "external",external: true, andplain_englishderived from itspurpose. Theidandnamecarry over. These nodes anchor the right side of the diagram. - For each feature (and the external nodes from step 2), look at its files and find:
- Imports / requires between features (frontend feature importing helpers from another feature)
- API calls: frontend code that calls
/api/...orfetch(...). Match the URL to the API feature that serves it. - Database access: any feature that imports the DB client, runs SQL, or uses an ORM. Connect it to the
Databasefeature. - External service calls: any feature that uses an SDK like
stripe.*,openai.*,anthropic.*,supabase.*, etc. Connect to the matching external node from step 2.
- Build a directed graph:
from_feature_id→to_feature_idwith a label that says what flows in plain English. Examples:- Login → Auth API: "sends username + password"
- Auth API → Database: "checks if user exists"
- Checkout → Stripe: "charges the credit card"
- Chat → OpenAI: "asks the AI to reply"
- Assign each feature a layer position so the diagram can be drawn top-down:
frontend→ top row (rank 0)api→ second row (rank 1)backend/ business logic → third row (rank 2)database→ fourth row (rank 3)external→ right side column (rank 1 visually, but flaggedexternal: true)
- For each feature, refine the plain_english sentence if you learned more from looking at its connections. Keep it under 20 words.
Output format (STRICT JSON to <output-dir>/graph.json)
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.
- 4d ago First seen · 86 lines · 37 tokens per session scan A 99be58a03760
boxbox-analyzer is an agent published in the GitHub repository aiunlocked1412/boxbox (26 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,052 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.