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 skills add shiggydoodah/skills --skill create-contextgit clone --depth 1 https://github.com/shiggydoodah/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/skills/shiggydoodah/skills/create-context)<a href="https://agentmods.dev/skills/shiggydoodah/skills/create-context"><img src="https://agentmods.dev/badge/skills/shiggydoodah/skills/create-context/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/skills/shiggydoodah/skills/create-context"><img src="https://agentmods.dev/badge/skills/shiggydoodah/skills/create-context.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.00076 | $0.00415 |
| Opus 5 | $0.00038 | $0.00208 |
| Sonnet 5 | $0.00015 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
create-context 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 8d 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
Creates one agent-only CONTEXT.md for a specific directory, then updates the
root CONTEXT-MAP.md so future agents can find it quickly.
Use map-context for a repo-wide context map. Use create-context when the
user points at one app, package, subsystem, or directory and wants a compressed
brief for that area.
Invocation
/create-context # create context for the current directory
/create-context apps/web # create context for one target directory
Process
- Resolve the target - use the provided path, or the current directory if
none is provided. Resolve the repo root with
git rev-parse --show-toplevel; if that fails, use the current working directory. - Inspect deeply - read enough source, tests, manifests, docs, and local configuration to understand the target's purpose, architecture, flows, integration points, and operational gotchas.
- Write one brief - create or replace
CONTEXT.mdat the target root. Do not create child contexts unless the user explicitly asks for them. - Upsert the map - create or update
CONTEXT-MAP.mdat the repo root, preserving unrelated entries and replacing only the target entry. - Report the result - summarize the target path, context file, map update, and any important limitations in what was inspected.
See REFERENCE.md for the required CONTEXT.md format, map
entry rules, and compression guidelines.
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.
- 8d ago First seen · 39 lines · 76 tokens per session scan A d2af0529e778
create-context is a skill published in the GitHub repository shiggydoodah/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 415 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…