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/xtsoftwarelabs/neatcontext-plugins/createnpx skills add XTSoftwareLabs/neatcontext-plugins --skill creategit clone --depth 1 https://github.com/XTSoftwareLabs/neatcontext-pluginsWhat 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.00045 | $0.00425 |
| Opus 5 | $0.00023 | $0.00212 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
create 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
Create context
Resolve <plugin-root> as two directories above the directory containing this file.
Keep this workflow distinct from $neatcontext:save: create starts from user-provided purpose and existing knowledge; save distills work already in the conversation.
Collect these inputs, asking one question at a time only for information the user has not already supplied:
- What the context covers, what Codex should do and avoid, and how it should behave.
- The path to an existing folder containing its knowledge.
- A short context name.
Run list before drafting so the routing description can distinguish adjacent contexts:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
Draft a Markdown profile beginning with # <name> and containing ## Purpose, ## What to do, ## What to avoid, and ## Behavior. Preserve the user's meaning and add no unsupported rules.
Draft one routing description under 200 characters. Describe scope only, using systems, symptoms, repos, ticket prefixes, and terminology someone would type. Make it contrastive with existing contexts. Do not include tone, behavior, or output-format instructions.
Show both drafts and wait for confirmation.
After confirmation, write the profile to a unique temporary Markdown file. Prefer a host scratch directory; otherwise use the workspace and remove the file after the CLI finishes. Run:
node "<plugin-root>/src/codex/neatcontext-cli.mjs" create --name "<name>" --knowledge "<folder>" --profile-from "<profile-file>" --use-when "<routing-description>"
Pass each value as one argument. On Windows, remove a trailing backslash from the knowledge-folder argument before quoting it.
Relay the result and remove only the temporary profile file. Do not connect the new context automatically.
What ships with it
1 file 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.
- 2d ago First seen · 39 lines · 45 tokens per session scan A 8e688842d3d4
create is a skill published in the GitHub repository XTSoftwareLabs/neatcontext-plugins (13 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 425 once invoked, about $0.0002 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
implement
Use when implementing a spec or GitHub ticket in this checkout.
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
run-smoke-tests
Run Playwright smoke tests, debug failures, and verify fixes. Use for smoke, e2e, Playwright, or pre-ship browser verification.
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
browser-use
Drive a real browser to QA a running app. Screenshots, clicks, forms, evidence. Use when there is no Playwright suite, or when a human flow must be walked.