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 OXI-717/ai-native-toolkit --skill setup-my-contextgit 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/setup-my-context)<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/setup-my-context"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/setup-my-context.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.1 | $0.00077 | $0.00897 |
| Opus 5 | $0.00039 | $0.00449 |
| Sonnet 5 | $0.00015 | $0.00179 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
setup-my-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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-my-context
Use this skill when a user wants to create or improve their own agent-working structure. The result is not a clone of someone else's setup. The result is a small, owned system that matches the user's projects, team, tools, and risk boundaries.
References
Read only what the current request needs:
- For the whole ladder, read references/ladder.md.
- For the interview flow, read references/bootstrap-interview.md.
- For workspace setup, read references/l0-workspace.md.
- For project context files, read references/l1-project-context.md.
- For memory and feedback loops, read references/l2-memory-feedback.md.
- For skills, commands, and delegation, read references/l3-delegation.md.
- For PR/review/acceptance pipelines, read references/l4-delivery-pipeline.md.
Operating Modes
Choose the smallest mode that fits the user's request.
Bootstrap
Use when the user is starting from scratch or says "set up my context".
- Read
bootstrap-interview.mdandladder.md. - Ask the minimum useful questions. Prefer batching obvious setup facts into one concise checklist only when the user explicitly asks you to proceed autonomously.
- Identify the target level:
- L0-L2 for non-technical users or teams that mainly need repeatable context.
- L0-L4 for technical users who want delegated implementation and PR flow.
- Generate concrete files or patches in the target workspace.
- End with the "done when" checks for every completed level.
Improve Existing Setup
Use when the user already has AGENTS.md, rules/, or skills.
- Inspect the existing files before proposing changes.
- Read the level reference that matches the missing or weak area.
- Keep edits narrow. Do not reorganize unrelated projects.
- Preserve user-specific conventions that are working.
What ships with it
8 files 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.
- 6d ago First seen · 102 lines · 77 tokens per session scan A 33e8d935ac40
setup-my-context is a skill published in the GitHub repository OXI-717/ai-native-toolkit (8 stars, last pushed 14d ago), licensed MIT. It adds 77 tokens to every session and 897 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
agents-md-revise
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end…
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.
feature-knowledge
Structures codebase exploration into a feature knowledge base.
performance
This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
rust
This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "Result/Option", "traits", or discusses memory safety and type-driven design. Provides patterns for ownership, error handling, type system usage, and safe concurrency.
self-improving-agent
Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills. Use when: (1) reviewing what Claude has learned about your project, (2) graduating a pattern from notes to…