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 doodledood/manifest-dev --skill figure-outgit clone --depth 1 https://github.com/doodledood/manifest-devWrote 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/doodledood/manifest-dev/figure-out)<a href="https://agentmods.dev/skills/doodledood/manifest-dev/figure-out"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/figure-out.svg" alt="Measured on agentmods" 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.00078 | $0.05681 |
| Opus 5 | $0.00039 | $0.02840 |
| Sonnet 5 | $0.00016 | $0.01136 |
| Haiku 4.5 | $0.00008 | $0.00568 |
Grade A, and why
figure-out 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The loop
Press from the true root
Press the topic relentlessly and preserve every unresolved evidence, hypothesis, genuinely viable rival, commitment question, and patch of fog that could still change the Read. Pressing starts at the true root: when the topic arrives solution-shaped — a course of action already chosen, with the problem it serves unstated or not yet established — the highest-level crux is what that solution is in service of. Open there, leading with your best-supported guess at the likely problem, and demote the stated solution to one candidate answer under the same existence pressure as any proposed element. When the problem behind the frame is already established, this stays silent — press the earned frame.
Challenge structure before designing it
When the conversation turns toward a solution, establish whether each proposed requirement, component, mechanism, or process step earns its place before designing it. Keep it when its benefit justifies its cost under the goal and constraints; otherwise remove it or fold it into something simpler. Resolve that question from available evidence where possible; bring it to the user when their judgment would change the answer. A child probe may be needed to settle the parent. Apply the same test as meaningful children emerge.
Classify constraints before they prune
Stated constraints get a kindred check before they prune: when one would remove genuinely viable options and its grounding is unstated, establish what kind of claim it is — hard (owned, verified, externally imposed) or assumed (inherited, habitual, a preference in disguise) — before letting it narrow the option set. Classify, never re-litigate: a constraint established as hard prunes exactly as it should, and one whose grounding is already established needs no interrogation.
Which question next
Tackle the next load-bearing question first, preferring the highest-level unresolved crux: settle the parent question before its children, and go deeper only when the parent is resolved or a subquestion is needed to resolve it; within a level, prefer the question whose answer would shift the read most.
What ships with it
14 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.
- references/ADR_FORMAT.md 11 KB
- references/autonomous.md 5.7 KB
- references/LOG.md 3.7 KB
- references/slack-mrkdwn.md 2.3 KB
- references/TASTE.md 6.5 KB
- references/team.md 4.6 KB
- references/WITH_DOCS.md 13 KB
- tasks/BUG.md 962 B
- tasks/CODING.md 1.6 KB
- tasks/DIAGNOSIS.md 2.7 KB
- tasks/FEATURE.md 1.5 KB
- tasks/REFACTOR.md 1.2 KB
- tasks/RESEARCH.md 1.5 KB
- tasks/TECH_DESIGN.md 1.8 KB
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 1c4629bd8ac4
- 2d ago Changed · +2 lines 4c499fa0dd81
- 7d ago First seen · 161 lines · 78 tokens per session scan A 322230b861f6
figure-out is a skill published in the GitHub repository doodledood/manifest-dev (73 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 5,681 once invoked, about $0.0004 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
vertical-onboarding
Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…
create-handoff
Create handoff document for passing work to another session. ALWAYS use when the user says 'create a handoff', 'hand this off', 'save progress for later', 'I need to stop here', or when context usage is high (>60%) during implementation and work needs to continue in a fresh session.
setup-warp
Interactively configure Warp terminal as a Catalyst launcher. Checks Warp install, detects projects, interviews the user for display details (name/emoji/color/variants) and generates /.warp/tabconfigs/.toml files with session-naming and remote-control wiring. Idempotent — re-run to add or update projects.
morning-briefing
Generate a daily briefing markdown at thoughts/briefings/YYYY-MM-DD.md with six sections — Review yesterday, Surface decisions, Plan today, relay-dispatch candidates, Friction since last briefing, and Learnings since last briefing — synthesized from Linear, GitHub, Granola, Google Drive, Google Calendar, and the…
briefing-followup
Interactive walk-through of today's morning briefing. Loads the briefing markdown at thoughts/briefings/YYYY-MM-DD.md (built by morning-briefing), parses its decisions block, and walks the user through each open decision — approve / reject / defer, schedule a calendar entry, file a Linear ticket, launch a relay-ticket…
status
Use this skill when the user asks "where am I", "what's the current task", "what's blocking me", "show status", "what needs sign-off", or "what's next". Prints a snapshot of the active plan, gate, sign-off progress, and next action. Reads only — writes nothing.