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/mathews-tom/armory/decision-mapnpx 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.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 | $0.00145 | $0.02331 |
| Opus 5 | $0.00072 | $0.01166 |
| Sonnet 5 | $0.00029 | $0.00466 |
| Haiku 4.5 | $0.00015 | $0.00233 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 144 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 label, exactly one interaction label, blockers, visible owner, session claim, and closure state. Refer to maps and tickets by linked title, never a bare identifier. Type labels are decision-map:discussion, decision-map:research, decision-map:prototype, and decision-map:unblock. Interaction labels are authoritative: exactly one of decision-map:hitl or decision-map:afk; ticket bodies must not restate the interaction mode.
Prerequisites
Use gh --version and require gh 2.96.0 or newer only when the user explicitly selects GitHub as the tracker. Verify authentication with gh auth status before that path. frontier.py requires Python 3.12 and only the standard library. .docs/agents/issue-tracker.md, when present, is the authoritative backend choice. Otherwise store maps locally in .docs/decision-maps/<effort>/; select GitHub only when the user expressly asks for it. Do not infer GitHub selection from a remote or authentication. Report the selected backend once and mention project-context-setup when the choice should be persisted.
Probe GitHub capability before using native relationships. When older GitHub Enterprise or an older CLI rejects blockedBy, take the degraded path: generated child links in the map and Blocked by: #N lines in ticket bodies. The degraded index exists only to emulate absent tracker relationships.
What ships with it
18 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.
- evals/cases.yaml 2.6 KB
- references/claim-protocol.md 1.7 KB
- references/elicitation.md 794 B
- references/map-format.md 1.4 KB
- references/map-states.md 918 B
- references/research-resolution.md 689 B
- references/ticket-types.md 1.3 KB
- references/tracker-operations.md 2.4 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/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/test_claims.py 3.5 KB runs code
- tests/test_frontier.py 4.0 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.
- 4d 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 (316 stars, last pushed 6d ago), licensed MIT. It adds 145 tokens to every session and 2,331 once invoked, about $0.0007 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
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
pm-prioritize
Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do…
pm-roadmap
Сводит статус итерации, оценивает прогресс milestones, фиксирует изменения приоритетов, отслеживает зависимости и выдаёт roadmap в формате Now/Next/Later с атрибуцией задержек по 5 причинам, health score и фреймворком обрезки scope при нехватке ресурсов. User-invoked only — do NOT auto-trigger. Triggers on…
retro
Use when the user asks for "ретро", "обзор недели", or "что было за неделю" and the department needs a fact-based closeout plus its next Area goal.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…