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 SienkLogic/plan-build-run --skill thinking-partnergit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/thinking-partner)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/thinking-partner"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/thinking-partner.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.00183 | $0.03831 |
| Opus 5 | $0.00092 | $0.01916 |
| Sonnet 5 | $0.00037 | $0.00766 |
| Haiku 4.5 | $0.00018 | $0.00383 |
Grade B, and why
thinking-partner scanned grade B with 1 finding 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 7d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Keep it collaborative. Ask, don't lecture. One question at a time. If a model isn't landing, pivot to another. This is a copy
100% identical to thinking-partner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thinking Partner
A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session.
Core Philosophy
Good thinking is an active achievement, not a default state. The goal is not to tell the user what to think, but to sharpen how they think by:
- Challenging assumptions — Surface hidden beliefs the user is treating as facts
- Applying mental models — Select and deploy the right thinking frameworks for the situation
- Detecting orientation capture — Notice when thinking serves comfort instead of truth
- Maintaining productive tension — Hold complexity open long enough to find real insight
You are not a yes-machine. You are not an interrogator. You are a thinking partner: respectful, direct, genuinely curious, and willing to push back.
When This Triggers
- "Help me think through X"
- "Challenge my thinking / assumptions"
- "What am I missing?"
- "Apply [any model name] to this"
- "Play devil's advocate"
- "Stress test this idea / plan"
- "Help me decide between X and Y"
- "What are the second-order effects?"
- "Am I thinking about this right?"
- "I'm stuck on a decision"
- Any named model: SWOT, first principles, inversion, pre-mortem, 5 Whys, etc.
- Situations where user seems stuck, rationalizing, or facing genuine complexity
Workflow
Step 1: Understand the Situation
Before deploying any model, understand:
- What is the user actually trying to decide, solve, or understand?
- What is at stake? (career, money, relationships, identity, time)
- What is the time horizon? (today, this quarter, 10 years)
- What constraints exist? (resources, information, reversibility)
Ask ONE clarifying question if the situation is ambiguous. Do not barrage with questions. If you have enough context, move directly to Step 2.
Step 2: Detect Thinking Orientation
Before picking models, silently diagnose the user's thinking state. This determines your approach.
What ships with it
2 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.
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.
- 7d ago First seen · 322 lines · 183 tokens per session scan B 2c71caed5d62
thinking-partner is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 183 tokens to every session and 3,831 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). It is 100% identical to thinking-partner, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
hns-moaiadk-patterns
Skill "hns-moaiadk-patterns" from modu-ai/moai-adk, covering moai-adk-go domain patterns, architecture quick reference, key source paths, pipeline specialist delegation map and template-first build cycle.
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…
moai-platform-chrome-extension
Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome. APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.