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/dustinvk/wherefore/resolvenpx skills add DustinVK/wherefore --skill resolvegit clone --depth 1 https://github.com/DustinVK/whereforeWhat 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.00083 | $0.01610 |
| Opus 5 | $0.00042 | $0.00805 |
| Sonnet 5 | $0.00017 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
resolve 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wherefore: resolve
Close out an open question by updating its individual file in
wherefore/questions/, recording what was decided, why, and which discussion (if
any) contains the full context. The file's frontmatter is the single source of
truth.
No em dashes. Periods, commas, colons, semicolons, or parentheses instead. Firm project rule.
Never delete anything under a wherefore/ data dir. Retire, do not delete.
Frontmatter safety
When you fill resolution, emit it as a double-quoted, single-line string, escaping
embedded " as \" and \ as \\. An unquoted value containing : (colon-space)
or a leading -, #, [, {, or " makes YAML misparse and crashes the dashboard
viewer. If the answer will not fit on one line, keep resolution to a one-line
summary and move detail into a ## Resolution body section. status and
resolution_slug need no quotes.
Workflow
-
Find the question. Files are named
Q-NNN-short-slug.md(ID prefix plus a scannable slug), so glob by the ID rather than assuming the exact name:ls wherefore/questions/Q-042-*.md wherefore/questions/Q-042.md 2>/dev/null(the second path catches any legacy file still namedQ-NNN.md). Expect exactly one match; open it. If nothing matches, say so clearly. To list what is open, dump the question frontmatter and filterstatus: open:for f in wherefore/questions/Q-*.md; do awk -v F="$f" 'BEGIN{print "=== " F " ==="} /^---[[:space:]]*$/ { n++; if (n==2) exit; next } n==1 { print }' "$f" doneConfirm the target's current
status. Ifstatus: resolved, tell the user and show the existing resolution; don't overwrite it. -
Get the resolution. Ask the user (or extract from context if they already provided it):
- Answer: what was decided, in one sentence.
- Why: the rationale or constraint that drove it, in one or two sentences. This is the part that matters months later; don't skip it.
- Source discussion (optional): a discussion slug if the answer came out of
a logged discussion. The user can name it, or you can check whether they just
ran the
captureskill and a fresh entry exists. If no wherefore entry captures it, the resolution is standalone.
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 · 121 lines · 83 tokens per session scan A f5d67d70151a
resolve is a skill published in the GitHub repository DustinVK/wherefore (1 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 1,610 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-31.
Other skills, from other repositories
decision-backfill
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
decision-memory
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
bootstrap
Scaffold or retrofit documentation-led conventions (AGENTS.md, CLAUDE.md, CONVENTIONS.md, ADR catalogue, plan/ queue, agent/ coordination) into a repo. Use when the user asks to "set up conventions", "bootstrap ADRs", "scaffold the documentation-led layout", "add AGENTS.md and a plan queue", or invokes /bootstrap.…
actual
Feature-complete companion for the actual CLI, an ADR-powered CLAUDE.md/AGENTS.md generator. Runs and troubleshoots actual adr-bot, status, auth, config, runners, and models, plus the Actual AI platform surface: login, logout, whoami, and advisor (org-scoped architecture Q&A). Covers all 5 runners (claude-cli…
code-review
Review pull requests in adrkit for actionable defects and conflicts with governing architecture decisions. Use during Copilot code review to inspect changed paths, retrieve relevant ADR context through the adrkit MCP server, and produce evidence-backed inline findings.
adr-integration
This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.