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/purenpx skills add tupe12334/instinct --skill puregit clone --depth 1 https://github.com/tupe12334/instinctWrote 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/tupe12334/instinct/pure)<a href="https://agentmods.dev/skills/tupe12334/instinct/pure"><img src="https://agentmods.dev/badge/skills/tupe12334/instinct/pure.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 | $0.00017 | $0.01507 |
| Opus 5 | $0.00009 | $0.00754 |
| Sonnet 5 | $0.00003 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
pure 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 3d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pure Goals
Overview
pure is a complementary goal-quality filter, often used alongside smart. It originates from NLP (neuro-linguistic programming) coaching and emphasizes the psychological and ethical framing of goals, not just their structure.
| Letter | Criterion | Core question |
|---|---|---|
| P | Positively stated | Is the goal framed as what you want (not what you want to avoid)? |
| U | Understood | Is the goal clear to everyone involved? |
| R | Relevant | Is it aligned with broader priorities and the right time? |
| E | Ethical | Does achieving this goal align with your values and not harm others? |
Criterion Breakdowns
P — Positively Stated
The brain moves toward what you focus on. Negatively framed goals ("stop missing deadlines", "don't lose customers") keep attention on the unwanted state.
Reframe toward the desired outcome:
| Negative framing | Positive reframe |
|---|---|
| "Stop being late to standups" | "Arrive to every standup on time" |
| "Don't lose the enterprise deal" | "Close the enterprise deal by [date]" |
| "Reduce bugs in production" | "Ship zero-defect releases" |
Test: Can you visualize and feel success? Negatively framed goals are hard to visualize.
U — Understood
The goal must be clear to every person who will act on it or be affected by it. No ambiguity in scope, ownership, or definition of done.
Test questions:
- If you asked every team member to describe this goal, would they give the same answer?
- Are all key terms defined? ("improve performance" — define "improve" and "performance")
- Is ownership explicit?
If interpretation varies: rewrite until consensus is possible.
R — Relevant
Right goal at the right time. Connects to the bigger picture.
Ask:
- Does this goal serve the current strategic priority?
- Is the timing right? (If a dependency isn't ready, the goal may be premature)
- Does pursuing this crowd out a higher-priority goal?
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.
- 3d ago First seen · 151 lines · 17 tokens per session scan A 894cf54369f7
pure is a skill published in the GitHub repository tupe12334/instinct (1 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 1,507 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.