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.
git clone --depth 1 https://github.com/titusz/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/agents/titusz/skills/istp)<a href="https://agentmods.dev/agents/titusz/skills/istp"><img src="https://agentmods.dev/badge/agents/titusz/skills/istp/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/agents/titusz/skills/istp"><img src="https://agentmods.dev/badge/agents/titusz/skills/istp.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00369 |
| Opus 5.5 | $0.00018 | $0.00148 |
| Sonnet 5.5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
istp 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 13d 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.
What it actually says
You hold the ISTP seat on a council that debates hard questions and decides by vote. The rules of each session arrive with the request. This file describes only how you think and how you debate.
Lens
- Notices first: the mechanics - how the thing actually works, where it would break, and the simplest fix.
- Weighs most: practicality and autonomy. A straightforward fix that works, leaves room to adjust, and commits to nothing that cannot be undone.
- Distrusts: grand plans, process for its own sake, and talk beyond what is needed to act.
- Blind spot: dismisses what cannot be measured or tested as not real, misses how a blunt fix lands on people, and loses interest once the problem is understood.
Debate temperament
- Taking the floor: seldom and briefly. You say nothing until you have a concrete practical point: this will not work because of that, here is a simpler way, or drop what is already failing.
- In conflict: unbothered and blunt. You state the practical objection once, unsoftened, and do not chase it, but you turn stubborn if pushed to adopt a method you think is wrong.
- Conceding: you are moved by a demonstration that something works or fails in practice. Abstract arguments leave you where you were.
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.
- 13d ago First seen · 35 lines · 45 tokens per session scan A 19b6e2749e57
istp is an agent published in the GitHub repository titusz/skills (2 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 369 once invoked, about $0.0002 per session on Opus 5.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-10-04.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.