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/outlinedriven/odin-claude-plugin/slicing-code-contextnpx skills add OutlineDriven/odin-claude-plugin --skill slicing-code-contextgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/slicing-code-context)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/slicing-code-context"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/slicing-code-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 | $0.00054 | $0.02483 |
| Opus 5 | $0.00027 | $0.01241 |
| Sonnet 5 | $0.00011 | $0.00497 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
slicing-code-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 yesterday.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slicing code context
Refuse first
- Reject source mutation: this skill returns proposed edits but never applies them.
- Reject broad or anchorless exploration: require an exact anchor and a focused task.
- Reject lexical approximations when parser-backed graph analysis is unavailable.
Contract
| Field | Bound contract |
|---|---|
| Trigger | A focused code question or patch proposal can be delegated using an exact symbol, path, entrypoint, or line-range anchor under a fixed source budget. |
| Authority | Read-only: no file, VCS, credential, paid, published, deployed, or remote mutation. |
| Side effect | A deterministic slice packet and one constrained worker response, with at most one coordinator-built replacement packet. |
| Done | Packet budget and boundaries validate, every worker claim and proposed edit cites included ranges, uncertain edges remain hypotheses, and consequential conclusions are independently checked by the coordinator. |
Inputs
- Target source tree root (required): canonical directory containing the source to slice.
- Anchor (required): one repository-relative
FILE:START-ENDline range, one exact path, one fully qualified symbol, or one exact entrypoint. - Worker task (required): concrete question or patch proposal whose answer can be checked from source.
- Mode and depth (optional):
neighborhooddepth 1 by default;upstreamordownstreamdepth 2–4;pathorentrypointdepth 10–20. - Peer anchor (required only for
path): exact second symbol or line range. - Budget (optional): positive integer estimated-token limit, default 8192.
Procedure
-
Validate the request. Canonicalize the target root. Reject an empty task, an anchor outside the root, an invalid or reversed line range, a mode/depth combination outside the table below, or
pathwithout a peer.Question Mode Depth Explain or review one unit with immediate context neighborhood1 exactly Who can reach this sink? upstream2–4 What behavior can this entry trigger? downstream2–4 How does one unit reach another? path10–20 Which public entrypoint reaches this target? entrypoint10–20
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.
- yesterday First seen · 142 lines · 54 tokens per session scan A a2d90f082c0d
slicing-code-context is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 2,483 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-09-04.
Other skills, from other repositories
automation-shape-routing
Front door for agent automation: choose inline, bounded fanout, reusable skill/workflow/gate, persistent agent-native workers, or explicit Gas City. Triggers: "build automation", "which orchestration shape", "should this use NTM".
toil-mining
Mine caller-supplied usage history for repeated toil and emit ranked evidence. Triggers: "mine toil", "find repeated operational work".
bootstrap
Initialize explicitly requested, missing AgentOps documentation and optional verdict storage without taking over repository workflow. Triggers: "bootstrap AgentOps", "initialize AgentOps docs".
operationalize
Distill repeated, evidence-backed expertise into a proposed skill, check, reference, or workflow artifact. Triggers: "operationalize this", "turn this expertise into a reusable capability".
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.