Claude Code Thinking Skills is a catalogue of 28 portable skills that give coding agents structured procedures for reasoning about decisions, diagnosis, risk, strategy, and related problems. It is intended for Claude Code, GitHub Copilot, Codex, Cursor, and other tools that support Agent Skills.
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 tjboudreaux/cc-thinking-skills --skill thinking-lindy-effectgit clone --depth 1 https://github.com/tjboudreaux/cc-thinking-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/tjboudreaux/cc-thinking-skills/thinking-lindy-effect)<a href="https://agentmods.dev/skills/tjboudreaux/cc-thinking-skills/thinking-lindy-effect"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-thinking-skills/thinking-lindy-effect/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/skills/tjboudreaux/cc-thinking-skills/thinking-lindy-effect"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-thinking-skills/thinking-lindy-effect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00035 | $0.00556 |
| Opus 5 | $0.00017 | $0.00278 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
thinking-lindy-effect 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 11d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lindy Effect
For non-perishable ideas, technologies, and practices, expected remaining life scales with current survival age. Prefer proven survivors unless the new option clears a burden of proof or the domain has drifted.
When to Use
- Choosing languages, frameworks, databases, protocols, patterns, or dependencies where long-term survival matters.
- Skill or architecture bets whose value depends on lasting relevance.
- Ranking options when ages differ materially and the choice outlives a short experiment.
When NOT to Use
- Perishable targets: specific SaaS vendors, hardware, fashion, or products that can shut down regardless of concept age.
- Active paradigm discontinuity where age in the old regime is weak evidence.
- Throwaway work where longevity is irrelevant — optimize for fit and speed.
- Treating "older" as "optimal for a new requirement"; survival predicts further survival, not best fit.
Procedure
- Confirm non-perishable scope. Concept/tech/practice continues; vendor/device → score fit/risk only and stop.
- Record survival age. First significant production use and current age (ecosystem-relative if the ecosystem is young).
- Form the Lindy prior. Expected remaining life ≈ current age; mark confidence from age and continued active use.
- Run domain-drift checks. Problem class changed? Paradigm shift invalidating old assumptions? New option uniquely closes a real present gap?
- Assign burden of proof. Default to the older adequate option. Accept newer only for a stated necessary advantage the Lindy option cannot meet at acceptable cost.
- Decide with residual risk. Pick primary; note impact if the prior is wrong and any fallback.
Stop condition: Primary chosen with age prior, drift check, and why new did or did not meet burden of proof.
Output
Options: <name, age, Lindy prior>
Drift: stable | discontinuous — <note>
Burden: on new | waived because <gap>
Decision: <primary>
Rejected: <one line each>
If Lindy wrong: <impact + fallback>
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.
- 11d ago First seen · 51 lines · 35 tokens per session scan A 82c22f0fdb5d
thinking-lindy-effect is a skill published in the GitHub repository tjboudreaux/cc-thinking-skills (1,300 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 556 once invoked, about $0.0002 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
forensic-read
Read any document the way a detective reads a witness statement — surface what it is NOT saying. Unlike a summarizer (which tells you what a text says), this skill exposes the subtext: hedging and weasel words, conspicuous omissions, buried leads, frequency tells, tone shifts, and non-answers. Use it on earnings…
pre-mortem
Find what will kill a plan before it's committed to — by assuming it already failed and working backwards to the causes. Based on Gary Klein's pre-mortem technique. Unlike generic "what are the risks?" brainstorming, this skill imagines a specific, vivid failure six months out, reasons back to the most likely causes…
second-order
Reason past the obvious, first-order consequence to the second-, third-, and long-tail effects everyone else stops short of. Where most analysis says "X causes Y", this skill asks "and then what?" — mapping the cascade, surfacing the non-obvious winners and losers, the reflexive responses, and the effects that only…
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.