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 johnqtcg/awesome-skills --skill constructive-thinkinggit clone --depth 1 https://github.com/johnqtcg/awesome-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/skills/johnqtcg/awesome-skills/constructive-thinking)<a href="https://agentmods.dev/skills/johnqtcg/awesome-skills/constructive-thinking"><img src="https://agentmods.dev/badge/skills/johnqtcg/awesome-skills/constructive-thinking.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.00170 | $0.03420 |
| Opus 5 | $0.00085 | $0.01710 |
| Sonnet 5 | $0.00034 | $0.00684 |
| Haiku 4.5 | $0.00017 | $0.00342 |
Grade A, and why
constructive-thinking 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 8d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
constructive-thinking
Turn messy thinking into a leader-ready structure. The skill teaches a method, not a writing template — the method compresses chaos into a five-element brief: Frame → Crux → Nodes → Tilt → Reasoning.
A senior leader does not have thirty minutes to absorb your story. They need you to put the structure on the table in three. This skill is the thinking discipline that makes that possible.
When to Use
Use this skill when the user is about to output something to an audience whose time is more valuable than their patience, and the raw material in their head is unstructured:
- Briefing a senior leader on a technical decision or status
- Pitching a proposal (RFC, ADR, project plan) and needs the one-page summary to land
- Reporting up after an investigation (not the formal postmortem — the verbal brief)
- Preparing slides or talk track for a presentation
- Summarizing a long thread / Slack / email storm for someone who only has 3 minutes
- Drafting an executive summary or TL;DR for any longer artifact
- Cross-functional update where the audience does not share your context
Trigger phrases observed in practice (CN + EN):
"向领导汇报", "整理思路", "做技术方案的 presentation", "做个 one-pager", "report up", "brief the boss", "summarize for leadership", "executive briefing", "TL;DR", "the main point"
When NOT to Use
Route to a different skill when:
| Situation | Use this instead |
|---|---|
| Writing the final polished document (RFC, runbook, API doc) | tech-doc-writer |
| Decomposing a feature into implementation steps | writing-plans |
| Conducting root cause analysis on a specific incident | incident-postmortem |
| Aggregating research with sources and citations | deep-research |
| Formatting a GitHub PR description | create-pr / commit |
| User wants to brainstorm freely — explore, not compress | (no skill — chat) |
A useful test: if the user is going to write something next, use tech-doc-writer. If they are going to speak to a human next, use this skill. If they are going to build something next, use writing-plans.
What ships with it
5 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.
- 8d ago First seen · 284 lines · 170 tokens per session scan A 36e329851967
constructive-thinking is a skill published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed today), licensed MIT. It adds 170 tokens to every session and 3,420 once invoked, about $0.0009 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
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.