What is armada-contract?

A guided process for writing a REQUIREMENTS.md feature contract. It records the goal, technology constraints, dependency-ordered phases, and checkable success criteria before implementation.

Use it to define a feature one question at a time, document its phases and tests or screenshots, and mark the contract approved before building.

It turns an idea into an agreed specification and prevents implementation from starting while the contract is still a draft.

armada-contract — Skill for Claude Code and Codex by rafmacalaba: A guided process for writing a REQUIREMENTS.md feature contract.

Install

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.

agentmods

npx agentmods add skills/rafmacalaba/armada/armada-contract

Any agent

npx skills add rafmacalaba/armada --skill armada-contract

Clone the repo

git clone --depth 1 https://github.com/rafmacalaba/armada

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-contract.svg)](https://agentmods.dev/skills/rafmacalaba/armada/armada-contract)

Your own site

<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-contract"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-contract.svg" alt="Measured on agentmods" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 363 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00033	$0.00363
Opus 5	$0.00016	$0.00181
Sonnet 5	$0.00007	$0.00073
Haiku 4.5	$0.00003	$0.00036

Measured 4d ago against content hash 4b76a5a6315a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

armada-contract 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.

src/skills/armada-contract/SKILL.md · 51 lines

What it actually says

You are co-writing an armada contract. The contract is the single source of truth for what to build.

Process

Ask the user what they want to build. One question at a time.
After each answer, reflect it back and ask the next logical question.
Cover: goal, stack constraints, phases, per-phase success criteria, final criteria.
Phases declare dependencies. Independent phases can run in parallel.
Success criteria must be demonstrable: a test run, a screenshot, or both.
When the user is satisfied, write armada/REQUIREMENTS.md with the contract.
The contract must carry Status: DRAFT until the user explicitly approves it.
Once approved, change status to Status: APPROVED. No implementation starts before approval.

Contract template

# Contract: <feature name>

Status: DRAFT
Commodore: <model>
Stack: <stack>

## Goal
...

## Phases (dependency-ordered)

### Phase 1 -- <name> (no deps)
- [ ] <task>
- [ ] ...
- **Success criteria:** ...

### Phase 2 -- <name> (depends on Phase 1)
- [ ] ...
- **Success criteria:** ...

## Final success criteria
1. ...
2. ...

Rules

Never start implementation against a DRAFT contract.
Keep it simple: small phases, clear criteria, no overengineering.
If the user wants a different feature later, use a separate contract file.

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.

4d ago First seen · 51 lines · 33 tokens per session scan A 4b76a5a6315a

Subscribe to this mod's changes

armada-contract is a skill published in the GitHub repository rafmacalaba/armada (92 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 363 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.

Planning Writing and docs ai-coding automation cli opencode orchestrator scaffolding

aoe

Use when launching, monitoring, or controlling AI coding agents (Claude Code, Codex, OpenCode, etc.) in tmux via Agent of Empires (aoe). Covers creating sessions, capturing agent output, running parallel worktree agents, and organizing work into groups and profiles. Prefer aoe over raw tmux for agent management.

agent-of-empires/agent-of-empires · 71 tokens

aoe

Manage AI coding agent sessions via Agent of Empires (aoe).

agent-of-empires/agent-of-empires · 17 tokens

debate

Structured adversarial analysis protocol. Quick single-agent modes (challenge, panel, pre-mortem, red team) plus a decision-review protocol where one agent proposes, one critiques, the proposer revises, and a binding/advisory judge panel decides ADOPT/REVISE/REJECT/ESCALATE.

EZotoff/ez-omo-config · 67 tokens

update-to-latest

Safety-critical operational pipeline for analyzing and executing OpenCode/OMO updates with explicit approval, patch preservation, rollback capability, and evidence-state discipline.

EZotoff/ez-omo-config · 33 tokens

patch-tracker

Track and verify custom patches to external dependencies. Register, audit, and verify patches survive updates. CRUD lifecycle for patch entries with post-update verification.