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 skills/rafmacalaba/armada/armada-ponytailnpx skills add rafmacalaba/armada --skill armada-ponytailgit clone --depth 1 https://github.com/rafmacalaba/armadaWrote 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/rafmacalaba/armada/armada-ponytail)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-ponytail"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-ponytail.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.00036 | $0.00323 |
| Opus 5 | $0.00018 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
armada-ponytail 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 6d 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
Armada Ponytail
Pragmatic code discipline for Galleon (backend-dev) and Clipper (frontend-dev). Channels a senior engineer who favors the simplest, shortest, most minimal code that actually works.
The Ponytail Ladder
Before writing new code, climb the ladder from top to bottom:
- Does this need to exist at all? Skip speculative features (YAGNI).
- Already in this codebase? Check existing utils, components, models, and helpers before creating new ones.
- Stdlib does it? Use native language standard library functions over custom helpers.
- Native platform feature covers it? Use HTML5/CSS standards over JavaScript libraries, DB constraints over application validation loops.
- Already-installed dependency solves it? Use installed packages. Never add a new dependency without orchestrator approval.
- Can it be one line? Prefer simple one-liners over multi-layered abstractions.
- Only then: Write the minimum code that passes tests.
Rules
- No unrequested abstractions: no single-implementation interfaces, no one-product factories.
- Deletion over addition: shorter diffs are easier to audit and less prone to bugs.
- Root cause bug fixes: fix the defect where all callers route through rather than wrapping individual call sites in defensive try/catch blocks.
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.
- 6d ago First seen · 27 lines · 36 tokens per session scan A 6581b24a9744
armada-ponytail is a skill published in the GitHub repository rafmacalaba/armada (95 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 323 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 skills, from other repositories
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
council
Full execution protocol for MODE: COUNCIL -- General Council research, parallel member dispatch, disagreement handling, and synthesis.
deep-research
Full execution protocol for MODE: DEEPRESEARCH — orchestrator-worker deep research over external sources: decompose, iterative websearch/webfetch retrieval, parallel sme synthesis, dual-reviewer claim verification, critic challenge of high-stakes claims, and a cited report. Loaded on demand by the architect when the…
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.