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/purposegit 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.00480 |
| Opus 5 | $0.00000 | $0.00240 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
purpose 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.
What it actually says
PUT TO OTHER USES
Generate ideas by asking what else this could be used for beyond its current purpose.
Instructions
Consider alternative applications, different markets, new contexts, and unconventional uses. What problems could this solve that it wasn't designed for?
Output Format
Subject: [What we're exploring]
Current Purpose
Primary use: [What it's designed/used for now] Current market: [Who uses it now]
Alternative Uses
Different Problems to Solve
| Current Problem Solved | Different Problem | How It Would Work |
|---|---|---|
| [problem A] | [problem B] | [adaptation needed] |
| [problem A] | [problem C] | [adaptation needed] |
| [problem A] | [problem D] | [adaptation needed] |
Different Markets
| Current Market | New Market | Appeal |
|---|---|---|
| [segment A] | [segment B] | [why they'd want it] |
| [segment A] | [segment C] | [why they'd want it] |
| [segment A] | [segment D] | [why they'd want it] |
Different Contexts
| Current Context | New Context | Application |
|---|---|---|
| [context A] | [context B] | [how to use] |
| [context A] | [context C] | [how to use] |
Waste/Byproduct Uses
| Waste/Byproduct | Potential Value | Who Wants It |
|---|---|---|
| [byproduct] | [use] | [market] |
Modified for Other Uses
| As-Is Limitation | With Modification | New Use |
|---|---|---|
| [limitation] | [change] | [use] |
Prompting Questions
- Who else could use this?
- What other problem does this solve?
- What market doesn't know they need this?
- Could children use this? Seniors? Businesses?
- What if we positioned this completely differently?
- What by-products or waste can be useful?
Top Alternative Use Ideas
- [Best idea]
- [Second idea]
- [Third idea]
$ARGUMENTS
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 · 73 lines · 0 tokens per session scan A 523c0b8e2450
purpose 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 480 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.