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 commands/neurofoo/agent-skills/categorizegit clone --depth 1 https://github.com/neurofoo/agent-skillsWhat 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.00000 | $0.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
categorize 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Categorize Problem Domain
Quickly determine which Cynefin domain a problem belongs to and what that means for how to approach it.
Instructions
Assess the characteristics of the problem to determine its domain, then provide the corresponding approach.
Output Format
Problem: [What we're categorizing]
Quick Domain Test
| Question | Answer | Points To |
|---|---|---|
| Is the right answer obvious or well-documented? | [Yes/No] | Simple if Yes |
| Would an expert know what to do after analysis? | [Yes/No] | Complicated if Yes |
| Can we only understand cause→effect in hindsight? | [Yes/No] | Complex if Yes |
| Is the situation unstable and urgent? | [Yes/No] | Chaotic if Yes |
| Are we genuinely unsure what kind of problem this is? | [Yes/No] | Confused if Yes |
Classification
Domain: [Simple / Complicated / Complex / Chaotic / Confused]
Confidence: [High / Medium / Low]
What This Means
Response Approach
| Domain | Your Approach |
|---|---|
| Simple | Sense → Categorize → Respond (use best practice) |
| Complicated | Sense → Analyze → Respond (consult experts) |
| Complex | Probe → Sense → Respond (run experiments) |
| Chaotic | Act → Sense → Respond (stabilize first) |
| Confused | Break down into sub-problems, categorize each |
For Your Problem
Approach: [The approach matching your domain]
First Step: [Immediate next action]
Common Mistake to Avoid: [What people typically do wrong in this domain]
Domain Indicators
Simple/Obvious
- Everyone agrees on the answer
- There's a standard process
- "We've done this before"
Complicated
- Experts can figure it out
- Analysis leads to answers
- Multiple good solutions exist
Complex
- Cause and effect unclear in advance
- Patterns emerge over time
- "It depends" is the honest answer
Chaotic
- High turbulence, no clear patterns
- Need to act immediately to stabilize
- No time for analysis
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 · 86 lines · 0 tokens per session scan A f8b1d863e23d
categorize is a command published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.