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-gemini-cli-extension/initnpx skills add OutlineDriven/odin-gemini-cli-extension --skill initgit clone --depth 1 https://github.com/OutlineDriven/odin-gemini-cli-extensionWrote 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-gemini-cli-extension/init)<a href="https://agentmods.dev/skills/outlinedriven/odin-gemini-cli-extension/init"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-gemini-cli-extension/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.00041 | $0.00382 |
| Opus 5 | $0.00020 | $0.00191 |
| Sonnet 5 | $0.00008 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
inits 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.
This is a copy
100% identical to inits — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Init - AGENTS.md Generator
Analyze this codebase and create or improve an AGENTS.md file for future ODIN Code Agent instances.
Core principle
Only encode knowledge that is expensive to rediscover. An agent can fd, rg, ast-grep, and read files in seconds. If the information is one search away, omit it.
Objective guard
AGENTS.md is for priming and guiding future agents with conventions, constraints, and rationale. It is not a repository summary.
What to include
- Cross-cutting conventions and boundaries that span multiple files.
- Implicit contracts and operational constraints that are easy to miss in quick code exploration.
- Non-obvious command guidance only when hidden constraints matter (required ordering, flags, env vars, caveats).
- For each included item, state:
- the rule or constraint
- why it exists (rationale)
What to omit (the agent can discover these)
- File trees, per-directory descriptions, or component inventories.
- Dependency/version tables.
- Generic development best practices.
- Information that is easily discoverable via search/read.
- Fabricated filler sections such as "Common Development Tasks", "Tips", or "Support".
- Any summary-style prose that restates code organization without conventions or rationale.
Workflow
- If
AGENTS.mdalready exists, suggest targeted improvements instead of rewriting. - Do not repeat yourself. Each fact appears once.
- Every statement must be grounded in files you actually read. Never invent.
- If uncertain, omit the claim rather than speculate.
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 · 42 lines · 41 tokens per session scan A 24cfc348a62d
inits is a skill published in the GitHub repository OutlineDriven/odin-gemini-cli-extension (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 382 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to inits, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
askme
Verbalized Sampling (VS) protocol for intent exploration before planning, mode-aware. Default exhaustive runs full VS; collaborative runs tip-sharing dialogue; adversarial walks the design tree one fork at a time. Auto-detects from phrasing ("help me refine" → collaborative, "poke holes" → adversarial); override via…
design
Set visual and interaction direction for any UI surface (web, React, TUI, CLI, desktop, Qt, design-system tokens) before any UI code. Direction-first: generates 3-4 distinct directions via verbalized sampling, picks one via per-axis single-select, then derives palette, typography, spacing, motion budget. Loads when…
git-branchless
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via git move, event-log recovery via git undo, deferred branch creation, speculative-merge git sync for base updates. Use when planning or executing multi-commit work, history rewrites, stack edits…
grill-ai-mastery
Hybrid interview that probes AI-engineering mastery by tip-vocabulary depth — entity referencing, loop closure, observability, harness improvement — not by token usage or LOC. Start collaborative (two-way tip exchange), escalate to adversarial probing when depth is lacking. Trigger when the user says "interview me on…
grill-me
Adversarial relentless interview against any plan or design until shared understanding is reached. Walk the decision tree, resolve dependencies one answer at a time, recommend a default per question. Trigger when the user says "grill me", "stress-test this", "interview me about this design", or otherwise asks for…
proof-driven
Proof-driven development. Use when implementing with formal verification using property-based testing, theorem proving, or proof tactics; zero unproven property policy enforced.