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 skills add pablocaeg/claude-army --skill challengegit clone --depth 1 https://github.com/pablocaeg/claude-armyWrote 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/skills/pablocaeg/claude-army/challenge)<a href="https://agentmods.dev/skills/pablocaeg/claude-army/challenge"><img src="https://agentmods.dev/badge/skills/pablocaeg/claude-army/challenge.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.1 | $0.00026 | $0.00328 |
| Opus 5 | $0.00013 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
challenge 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 7d 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
Simulate the lead reviewer's feedback on the current changes. Uses reviewer patterns from the forge analysis.
Before Starting
- Read
.context/forge-analysis.mdfor reviewer patterns - If it doesn't exist, tell the user to run
/claude-army:analyzefirst
Process
- Run
git statusandgit diff --name-onlyto find all changes - Read every changed/new file
- Apply reviewer checks in tier order (Tier 1 first, most likely to be raised)
- For factual claims (thresholds, tax classification, etc.): WebSearch to verify
- For source URLs: WebFetch to confirm accessibility
Output
Present findings as the lead reviewer would — questions, not demands:
## Review Simulation: [Reviewer Name]
### Questions (likely to ask)
**file:line** — [question in their voice]
Fix with: [which agent or direct edit]
### Issues (would flag)
**file:line** — [what's wrong]
Fix with: [which agent]
### What Looks Good
[acknowledge well-done parts]
### Fix Plan
| # | Issue | Fix Agent | Instruction |
|---|-------|-----------|-------------|
| 1 | ... | ... | ... |
Execution order: [dependencies]
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.
- 7d ago First seen · 47 lines · 26 tokens per session scan A d4425f6c7522
challenge is a skill published in the GitHub repository pablocaeg/claude-army (2 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 328 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-31.
Other skills, from other repositories
suede-code-review
Suede Labs AI findings-only code review with full context: changed files, callers, contracts, and deploy surface. Covers TypeScript, React, Next.js, database, Swift/iOS, OWASP, accessibility, SEO, observability, commit hygiene, and deploy risk, ranked P0-P3 with file:line evidence and a fix path. Use when asked to…
suede-code
Suede Labs AI combined code review and ship grade in one pass: findings with file:line evidence plus an A-F lane grade, Instant-F security triggers, OWASP checks, a deploy-safety gate, and fix briefs. Use when asked to review this, grade this, security-check this, is this safe to ship, or check this PR before merge …
suede-code-grader
Suede Labs AI blunt A-F ship grade for a code change across correctness, security and permissions, data and state, domain truth, UX and release behavior, tests and verification, and deploy readiness, with Instant-F triggers and evidence-based grade caps on auth, payment, migration, and public-API surfaces. Use when…
flo-simplify
Review changed code for reuse, quality, and efficiency, then fix any issues found. Sizes review effort to the diff — trivial edits get a self-review, substantial edits get parallel agents. Renamed from /simplify to avoid collision with Claude Code's built-in simplify skill.
architecture
Use when the user asks to improve architecture, find refactoring opportunities, surface deepening opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable. Surfaces shallow modules and hypothetical seams using a precise vocabulary (Module / Interface / Implementation /…
persona-panel
Use this skill when you need multi-persona parallel content review — domain experts, buyer personas, compliance reviewers, or custom catalog entries reviewing a target file or output. Dispatches N persona agents in parallel, consolidates verdicts via a configurable mode (voting-quorum, hard-gate-threshold, or…