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 Mathews-Tom/armory --skill decision-mapgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/decision-map)<a href="https://agentmods.dev/skills/mathews-tom/armory/decision-map"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/decision-map/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/skills/mathews-tom/armory/decision-map"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/decision-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.02941 |
| Opus 5.5 | $0.00034 | $0.01176 |
| Sonnet 5.5 | $0.00017 | $0.00588 |
| Haiku 4.5 | $0.00009 | $0.00294 |
Grade A, and why
decision-map 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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Map
Scope and Trigger Boundary
Ask one discriminator before creating anything: Do we know what should be built? If no, map unresolved decisions. If yes, route known design into milestones with plan-prompts or implementation-sized work with task-decomposer. A decision map produces decisions and evidence, never implementation deliverables.
| Situation | Package |
|---|---|
| Destination or design still unclear; decisions would have to be invented | decision-map |
| Design known; needs milestones and execution prompts | plan-prompts |
| Feature specified; needs implementation slices, tests, risks | task-decomposer |
| Plan exists; needs a pre-implementation audit | plan-review |
| Plan approved; needs execution across sessions | milestone-runner |
| Repo audit needs standalone remediation plans, optionally as issues | codebase-advisor --issues |
| One decision needs a durable record | adr-writer |
| Session state must survive a handoff | handoff |
Do not turn vague hopes into implementation tasks merely to make progress appear orderly. A sharp but currently unanswered question is a ticket. A question that cannot yet be stated sharply is fog.
Data Model
A map is one parent tracker item with five sections: Destination, Notes, Decisions so far, Not yet specified, and Out of scope. It is an index, not a duplicate store. A decision exists in exactly one ticket; the map holds only resolution pointers and scope boundaries.
A ticket holds one question, exactly one type, exactly one interaction mode, blockers, visible owner, session claim, and closure state. Refer to maps and tickets by linked title, never a bare identifier. Types are decision-map:discussion, decision-map:research, decision-map:prototype, and decision-map:unblock; interaction is exactly one of decision-map:hitl or decision-map:afk. On GitHub, labels are authoritative and are not duplicated in the body. Local tickets instead require the existing Type:, Interaction:, Status:, and Blocked by: headers. Read references/ticket-types.md before creating either backend's ticket body.
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHANGELOG.md 2.2 KB
- evals/cases.yaml 13 KB
- LICENSE 1.0 KB
- references/claim-protocol.md 2.9 KB
- references/elicitation.md 794 B
- references/map-format.md 1.4 KB
- references/map-states.md 957 B
- references/prototyping.md 4.5 KB
- references/research-resolution.md 689 B
- references/ticket-types.md 2.3 KB
- references/tracker-operations.md 4.9 KB
- references/upstream/LICENSE 1.0 KB
- references/upstream/provenance.md 2.5 KB
- scripts/frontier.py 17 KB runs code
- tests/fixtures/github_issues_degraded.json 2.3 KB
- tests/fixtures/github_issues.json 2.5 KB
- tests/fixtures/github_unresolved_prototype.json 1.8 KB
- tests/fixtures/local_map/001-pick-the-store.md 151 B
- tests/fixtures/local_map/002-schema-shape.md 163 B
- tests/fixtures/local_map/map.md 199 B
- tests/fixtures/unresolved_prototype/010-refund-state.md 1.1 KB
- tests/fixtures/unresolved_prototype/claims/10.lock 65 B
- tests/fixtures/unresolved_prototype/map.md 203 B
- tests/test_claims.py 3.5 KB runs code
- tests/test_frontier.py 8.4 KB runs code
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.
- yesterday Changed · +1 lines · +9 tokens per session bbd19bbe0e15
- 9d ago Changed · +8 lines · -68 tokens per session ffe2c0155e33
- 1mo ago First seen · 144 lines · 145 tokens per session scan A e13b59fd07ce
decision-map is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 2,941 once invoked, about $0.0003 per session on Opus 5.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
weekly-retro
A structured weekly retrospective for a one-person business run with AI agents. It gathers evidence from code, project tools, and canonical business files, then records findings and outcomes.
openagentskill-registry
Discover, compare, audit, and safely install reusable AI Agent Skills with OpenAgentSkill. Use whenever an agent needs a capability it does not already have, must compare Skill alternatives, or needs evidence before installing third-party instructions.
corp-new
A workflow for creating a new department folder inside a local agent headquarters, with its own rules, skills, tasks, and links back to the headquarters.
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
make-landing
A design workflow for creating several visual versions of a landing page, hero area, cover, or slide surface. Each version is previewed, shown to a person for selection, and the chosen direction is then applied to the main project.
audit-agent-rules
A skill that audits agent instruction files and the skills an agent sees when it starts, then reports what to remove, move, or rewrite. It edits files only after the user agrees.