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/tupe12334/instinct/scqanpx skills add tupe12334/instinct --skill scqagit clone --depth 1 https://github.com/tupe12334/instinctWhat 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.00022 | $0.02159 |
| Opus 5 | $0.00011 | $0.01079 |
| Sonnet 5 | $0.00004 | $0.00432 |
| Haiku 4.5 | $0.00002 | $0.00216 |
Grade A, and why
scqa 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCQA (Situation → Complication → Question → Answer)
Overview
SCQA is a narrative opening structure from Barbara Minto's Pyramid Principle. It hooks the audience by establishing shared ground (Situation), introducing tension (Complication), crystallizing the implied question (Question), and delivering the answer upfront (Answer). The result is communication that earns attention instead of demanding it.
┌─────────────────────────────────────────────────────────────┐
│ S ──► C ──► Q ──► A │
│ │
│ Situation Complication Question Answer │
│ (agreed (something (what the (your │
│ context) changed or audience is governing │
│ went wrong) now asking) message) │
└─────────────────────────────────────────────────────────────┘
Tension builds across S → C → Q, then releases at A.
Use SCQA to open executive briefings, emails to senior stakeholders, consulting decks, product proposals, and any communication where you need to be read — not skimmed.
Element Breakdowns
S — Situation
State facts the audience already accepts as true. This is not your argument — it is shared ground that anchors everything that follows.
Include:
- The stable background state before anything went wrong
- Scope: the business, team, product, or market being discussed
- Enough context for the audience to recognize the world you are describing
Keep it to 1–3 sentences. If the audience challenges anything in your Situation, you have started too far into disputed territory — move earlier.
Bad: "Our product is struggling and we need to fix it." Good: "For the past two years, our enterprise tier has been our highest-margin segment, accounting for 60% of ARR."
C — Complication
Introduce the tension that makes the Situation unstable. This is the reason you are communicating at all.
Types of complications:
- Something changed (market shift, new competitor, regulation)
- Something failed (metric missed, project slipped, assumption proven wrong)
- Something is about to happen (deadline, board review, contract renewal)
- A contradiction emerged (two true things that cannot both stand)
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 · 166 lines · 22 tokens per session scan A b3a16447c3a0
scqa is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 2,159 once invoked, about $0.0001 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
thinking-model-router
When unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).
thinking-red-team
For authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.
thinking-scientific-method
When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
thinking-systems
When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
thinking-circle-of-competence
Use when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain — never confabulate.
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.