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/rcelebrone/DotAgentsWrote 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/commands/rcelebrone/dotagents/dot-agent-architecture-review)<a href="https://agentmods.dev/commands/rcelebrone/dotagents/dot-agent-architecture-review"><img src="https://agentmods.dev/badge/commands/rcelebrone/dotagents/dot-agent-architecture-review/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/commands/rcelebrone/dotagents/dot-agent-architecture-review"><img src="https://agentmods.dev/badge/commands/rcelebrone/dotagents/dot-agent-architecture-review.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.00028 | $0.00225 |
| Opus 5 | $0.00014 | $0.00112 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
dot-agent-architecture-review 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 10d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 12 lines · 28 tokens per session scan A b37a53ebb5d0
dot-agent-architecture-review is a command published in the GitHub repository rcelebrone/DotAgents (14 stars, last pushed 1mo ago), with no licence file. It adds 28 tokens to every session and 225 once invoked, about $0.0001 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 commands, from other repositories
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
prepare-review
Package codebase for external review using RepoMix.
review_prs
Hold the same bar as reviewpr: a Principal AWS Solutions Architect who is direct, specific, justifies every concern with a concrete risk and a file:line, distinguishes blocking issues from nits, and never rubber-stamps. This command orchestrates that single-PR review across a set of PRs — it does not restate the…
review_pr
Review as a Principal AWS Solutions Architect. You have deep expertise in AWS CDK and TypeScript, serverless and container compute, security/IAM least-privilege, cost, and operational excellence. You hold a high bar: correctness and long-term maintainability over short-term convenience. You are direct, specific, and…
lfe-complexity-check
Inspector sub-skill. Analyses changed code for cyclomatic complexity, excessive nesting, oversized functions, and cognitive load indicators. Pure LLM reasoning — no external tooling. Writes .plans/checks/complexityfindings.md. Called by lfe-inspector when enabled in inspector-config.md.
lfe-hygiene
Conduct a structural audit of the repository to detect "Documentation Drift" or "Spaghetti Files." Use in Phase 5 (Hygiene sub-pipeline, Step 1).