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/fakoli/fakoli-plugins/resolve-decisionsnpx skills add fakoli/fakoli-plugins --skill resolve-decisionsgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/resolve-decisions)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/resolve-decisions"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/resolve-decisions.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.00101 | $0.03038 |
| Opus 5 | $0.00051 | $0.01519 |
| Sonnet 5 | $0.00020 | $0.00608 |
| Haiku 4.5 | $0.00010 | $0.00304 |
Grade A, and why
resolve-decisions 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 2d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve Decisions — Walk Open Items as Q&A
Turn every [NEEDS DECISION] marker, unresolved ## Open Question, or missing acceptance-criterion into a one-question conversational turn — propose options when the surrounding context lets you, accept the user's pick, and apply the answer to prd.md. The agent does the framing and the typing; the user does the deciding.
The anti-pattern this skill exists to prevent: handing the user a list of "open questions to resolve in your editor first" and then waiting. An LLM's strength over a CLI is turning blocked on a decision into let me ask you the right question. Pasting a to-do list of unresolved decisions is the same failure mode as pasting a to-do list of CLI commands.
When to Use
- After
fakoli-state prd parsesucceeds and the agent notices unresolved items (prdskill Step 3 routes here whenfind_decisionsreturns non-empty). - Before
fakoli-state planruns, whenfind_decisionsreports[NEEDS DECISION]markers or unresolved Open Questions that would shape task generation (planskill Step 0 routes here). - When the user explicitly asks to "resolve open questions", "answer the NEEDS DECISION items", or "fill in the missing acceptance criteria".
- When
fakoli-state review tasksblocks tasks for missing acceptance criteria or verification commands — those becomemissing_fielddecisions this skill can drive Q&A on, instead of asking the user to re-edit the PRD by hand.
Do not use this skill to author requirements from scratch — use start-prd. Do not use this skill to score or expand tasks — that is the plan skill's job. Do not use this skill to make apply --approve decisions — that is the finish skill's gate.
Prerequisites
.fakoli-state/prd.md must exist and parse cleanly. Confirm:
fakoli-state prd parse 2>&1 | tail -3
The detector is at bin/src/fakoli_state/planning/decisions.py; the CLI surface is fakoli-state prd find-decisions; the MCP equivalent is the find_decisions tool.
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.
- 2d ago First seen · 182 lines · 101 tokens per session scan A a6bb33ac6580
resolve-decisions is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 101 tokens to every session and 3,038 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
arch-knowledge-patch
Restart the daemon immediately after upgrading openssh to 9.8p1 because the old daemon cannot accept new connections.
axum-knowledge-patch
Axum 0.8 uses return-position impl Trait in FromRequestParts and FromRequest. Implement their methods with native async fn; do not retain the old #[asynctrait] annotation.
caddy-knowledge-patch
Use this patch when writing or reviewing Caddyfile or JSON configuration, upgrading Caddy, building custom binaries, or operating Caddy's HTTP, proxy, certificate, and telemetry features.
cloudflare-d1-knowledge-patch
Use this skill when designing, implementing, migrating, operating, or debugging Cloudflare D1 databases. Check the project’s Wrangler configuration, binding usage, database generation, account plan, and remote-versus-local command flags before applying guidance.