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.
git clone --depth 1 https://github.com/product-on-purpose/thinking-framework-skillsWrote 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/commands/product-on-purpose/thinking-framework-skills/think-issue-position-argument-mapping)<a href="https://agentmods.dev/commands/product-on-purpose/thinking-framework-skills/think-issue-position-argument-mapping"><img src="https://agentmods.dev/badge/commands/product-on-purpose/thinking-framework-skills/think-issue-position-argument-mapping/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/commands/product-on-purpose/thinking-framework-skills/think-issue-position-argument-mapping"><img src="https://agentmods.dev/badge/commands/product-on-purpose/thinking-framework-skills/think-issue-position-argument-mapping.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.00052 | $0.00598 |
| Opus 5 | $0.00026 | $0.00299 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
think-issue-position-argument-mapping 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 9d 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.
What it actually says
Run the think-issue-position-argument-mapping recipe: 3 skills chained in a fixed order, carrying forward only the compressed artifact at each handoff.
The compression is the point. Do not paste a whole artifact into the next step; carry exactly what each handoff names, so the chain stays cheaper and sharper than running the skills back to back.
IBIS (Issue-Based Information System; Kunz and Rittel, 1970), and the facilitated practice built on it ("Dialogue Mapping", a term associated with Jeff Conklin and the CogNexus Institute), is not a separate skill here: its three node types are each a move the library already ships, and the only residue is the link grammar wiring them together - the shape of a chain, not a separable cognitive move. This recipe runs that chain honestly rather than dressing the notation up as a new method. The descriptive name avoids the branded term; the IBIS notation itself is generic published work.
Run the steps in order, carrying forward only the compressed artifact between them, and recurse where an argument raises a new issue:
think-issue-tree(Issues) -> carry the set of open questions the deliberation is actually contesting. Relax the MECE constraint: IBIS issues need not partition cleanly, they just need to be the real questions in play. (On a raw transcript, surface them by question rather than by decomposition.)think-decision-option-review(Positions) -> for each issue, carry the rival candidate answers. This is the option-enumeration front of the skill; you are listing the positions, not yet scoring to a single winner.think-argument-mapping(Arguments) -> for each position, carry the pro and con arguments with their inference structure. Argument-mapping does strictly more than the IBIS pro/con layer (it excavates co-premises and flags weak links); take that as a bonus, not a mismatch.
Composite artifact: a typed deliberation map - issues, the positions answering each, and the arguments supporting or attacking each position - assembled from shipped moves, navigable where the raw debate was tangled. Full prose and rationale: recipes/issue-position-argument-mapping.md.
Apply the chain to: $ARGUMENTS
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.
- 9d ago First seen · 23 lines · 52 tokens per session scan A b15960b2dbf1
think-issue-position-argument-mapping is a command published in the GitHub repository product-on-purpose/thinking-framework-skills (15 stars, last pushed 23d ago), licensed Apache-2.0. It adds 52 tokens to every session and 598 once invoked, about $0.0003 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 commands, from other repositories
doff
Doff the current masque and return to baseline Claude.
speckit.polish
Polish and complete speckit workflow — quality gate, docs, changelog, MR.
review
Recent git commits: !git log --oneline -10.
health
Check running Claude Code or Codex sessions, find zombies, offer to clean up safely.
quick
Quick 10-second context health check with quality score and top issues.
session-recap
Summarize recent CHANGELOG.md entries for context restoration. Parses the canonical heading shape ## YYYY-MM-DD — pass-N — summary. Filters: last N (default 10), YYYY-MM date prefix, or "today". Supports --json for machine-readable output.