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/oxi-717/ai-native-toolkit/ctx-initnpx skills add OXI-717/ai-native-toolkit --skill ctx-initgit clone --depth 1 https://github.com/OXI-717/ai-native-toolkitWrote 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/oxi-717/ai-native-toolkit/ctx-init)<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/ctx-init"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/ctx-init.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.00055 | $0.00815 |
| Opus 5 | $0.00028 | $0.00407 |
| Sonnet 5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
ctx-init 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctx-init — context initialization in a repo
Creates the ctx structure in the current repo:
AGENTS.mdfrom template with frontmatter (all@-imports are relative@./rules/...)CLAUDE.mdwith@AGENTS.mdimportrules/with copies of shared plugin rules (language,dates,git,no-secrets,no-public-names) plus project-specific stubs (stack,testing,boundaries,focus)
Both shared rules and templates exist in two language variants: en/ (English) and ru/ (Russian). The user picks one at init time. Shared rules are copied rather than imported via ${CLAUDE_PLUGIN_ROOT} because Claude Code does not expand env variables in project-level @-imports (and this is needed for cross-agent compatibility: Codex/Gemini/Cursor all read the same AGENTS.md).
Input (ask the user before running)
- project — short name (e.g.
MYAPP,API,DOCS). - description — one line describing the project topic.
- language —
enorru(defaulten). Determines the language ofAGENTS.mdheaders, the 5 shared rule files (language,dates,git,no-secrets,no-public-names), and the 4 project stubs (stack,testing,boundaries,focus).
Procedure
Pre-flight checks:
pwdmust be the root of the repo being initialized.- If
AGENTS.mdalready exists — stop and tell the user that migration is not supported. Ask the user to rename the old file manually (mv AGENTS.md AGENTS.md.legacy) and callctx-initagain.
Actions (replace <LANG> with the chosen en or ru):
- Copy
${CLAUDE_PLUGIN_ROOT}/templates/<LANG>/AGENTS.md.templateto./AGENTS.md. - Substitute
{{PROJECT}},{{DESCRIPTION}}viased. - Copy
${CLAUDE_PLUGIN_ROOT}/templates/<LANG>/CLAUDE.md.templateto./CLAUDE.md. - Create
./rules/. - Copy shared rules:
${CLAUDE_PLUGIN_ROOT}/rules/<LANG>/*.mdto./rules/. - Copy project stubs:
${CLAUDE_PLUGIN_ROOT}/templates/<LANG>/stubs-repo-rules/*.mdto./rules/(without overwriting shared files). - Run
python3 ${CLAUDE_PLUGIN_ROOT}/lib/ctx-lint.py <repo>— verify all@-imports resolve (0 errors). - Show the user what was created, and ask them to fill in the
rules/stack.md,rules/testing.md,rules/boundaries.md,rules/focus.mdfiles. - Do not commit automatically — user reviews and commits themselves.
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.
- 5d ago First seen · 49 lines · 55 tokens per session scan A 4944400f7511
ctx-init is a skill published in the GitHub repository OXI-717/ai-native-toolkit (7 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 815 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-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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…