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 tomzx/agents --skill make-decisiongit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/make-decision)<a href="https://agentmods.dev/skills/tomzx/agents/make-decision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/make-decision/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/tomzx/agents/make-decision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/make-decision.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01000 |
| Opus 5.5 | $0.00014 | $0.00400 |
| Sonnet 5.5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
make-decision 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 22d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make Decision
The single decision skill reused across the PDLC. It handles two cases:
- Gate decisions — invoked at every phase boundary to decide
proceed/pivot/kill. - General product decisions — any consequential choice (positioning, segmentation, trade-offs) recorded for traceability.
One record format, one storage location (.pdlc/decisions/).
The difference is purely whether the frontmatter carries a gate_verdict tied to a phase.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - For a gate: the phase artifact just produced, and the initiative it belongs to.
- For a general decision: the context and options under consideration.
Steps
- Identify whether this is a gate or a general decision. A gate is invoked by the orchestrator right after a phase skill completes its artifact.
- For a gate decision, evaluate the opportunity's continued viability using the gate criteria below. The artifact's prose quality is the phase skill's job (it self-checks); this gate judges whether the opportunity still deserves to move forward.
- For a general decision, capture context, at least two options, the choice, trade-offs, and consequences (use the decision template).
- Write the record to
.pdlc/decisions/N-<slug>.mdwhereNis the next unused number. Use the template atskills/pdlc/templates/decision.md. - Set frontmatter per the gate table below when this is a gate.
Gate Criteria
A proceed requires all of:
- The phase artifact answers the phase's question (Discover: is there a real problem? Validate: does evidence support the hypothesis? Strategy: is this the right focus? Define: is the scope buildable and outcome-linked? Launch: is the market ready? Measure: did we move the metric without breaking guardrails?).
- No unresolved blocker that would waste the next phase's effort.
- The estimated cost of the next phase is justified by the opportunity's expected value.
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.
- 22d ago Changed · +13 lines 34619431f4ba
- 24d ago Changed c5da8708defd
- 1mo ago First seen · 83 lines · 35 tokens per session scan A 7bac45ef865c
make-decision is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,000 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.