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/tkellogg/open-strix/introspectionnpx skills add tkellogg/open-strix --skill introspectiongit clone --depth 1 https://github.com/tkellogg/open-strixWrote 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/tkellogg/open-strix/introspection)<a href="https://agentmods.dev/skills/tkellogg/open-strix/introspection"><img src="https://agentmods.dev/badge/skills/tkellogg/open-strix/introspection.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.00060 | $0.02098 |
| Opus 5 | $0.00030 | $0.01049 |
| Sonnet 5 | $0.00012 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
introspection 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Introspection
You are a stateful agent. Your behavior leaves traces in structured logs. This skill teaches you to read those traces to diagnose problems, understand your own patterns, and improve.
Source of Truth Hierarchy
logs/events.jsonl— Ground truth. Every tool call, error, and scheduler event is recorded here with timestamps and session IDs.logs/journal.jsonl— Your interpretation of what happened. Useful for intent and predictions, but it's narrative, not fact.- Discord message history — What was actually sent and received. Use
list_messagesto verify. scheduler.yaml— Current scheduled job definitions.- Memory blocks — Your current beliefs about the world. May be stale.
When sources conflict, trust events > Discord history > journal > memory blocks.
Key Log Schemas
events.jsonl
Each line is a JSON object:
{
"timestamp": "2026-03-01T12:00:00+00:00",
"type": "tool_call",
"session_id": "abc123",
"tool": "send_message",
"channel_id": "123456",
"sent": true,
"text_preview": "first 300 chars..."
}
Common event types:
tool_call— Any tool invocation (checktoolfield for which one)tool_call_error— A tool that failed (checkerror_type)send_message_loop_detected— Circuit breaker caught repeated messagessend_message_loop_hard_stop— Turn terminated for safetyscheduler_reloaded— Jobs were reloaded from scheduler.yamlscheduler_invalid_job— A job failed validationscheduler_invalid_cron— Bad cron expressionscheduler_invalid_time— Bad time_of_day value
journal.jsonl
Each line:
{
"timestamp": "2026-03-01T12:00:00+00:00",
"session_id": "abc123",
"channel_id": "123456",
"user_wanted": "what the human asked for",
"agent_did": "what you actually did",
"predictions": "what you think will happen next"
}
scheduler.yaml
jobs:
- name: my-job
prompt: "Do the thing"
cron: "0 */2 * * *" # OR time_of_day, not both
channel_id: "123456" # optional
What ships with it
3 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.
- 4d ago First seen · 205 lines · 60 tokens per session scan A 238a139087b0
introspection is a skill published in the GitHub repository tkellogg/open-strix (85 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 2,098 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…