Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add luis-at-safebase/luism-claude-plugins/plugin install iodaWrote 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/luis-at-safebase/luism-claude-plugins/ioda-init)<a href="https://agentmods.dev/skills/luis-at-safebase/luism-claude-plugins/ioda-init"><img src="https://agentmods.dev/badge/skills/luis-at-safebase/luism-claude-plugins/ioda-init/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/luis-at-safebase/luism-claude-plugins/ioda-init"><img src="https://agentmods.dev/badge/skills/luis-at-safebase/luism-claude-plugins/ioda-init.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.00028 | $0.01283 |
| Opus 5 | $0.00014 | $0.00642 |
| Sonnet 5 | $0.00006 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
ioda-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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User's request: $ARGUMENTS
Initialize ioda
You are setting up ioda configuration for this machine. Run this wizard step by step. Use the AskUserQuestion tool for every multiple-choice question — do not ask questions in plain text.
Step 0: Check existing configuration
Run:
cat "$HOME/.ioda/config.json" 2>/dev/null || echo "NOT_CONFIGURED"
If config exists and --reset was NOT passed: use AskUserQuestion to ask whether to reconfigure. If the user keeps current config, exit with "Configuration unchanged."
If NOT configured (or user chose to reconfigure): proceed to Step 1.
Step 1: Storage location
Use AskUserQuestion to ask where artifacts should live. Offer:
- Default —
~/.ioda/features/(tool-owned, easy cleanup) - Custom path — any absolute path. Common options: an Obsidian vault, Logseq graph, or notes directory.
If the user picks custom, prompt them for the absolute path. Expand ~ to $HOME. Strip trailing slashes.
Store as base_dir.
Step 2: Ticket CLI fetch command
Use AskUserQuestion to ask how ioda should fetch ticket information. Offer:
- Skip — always paste ticket contents manually
- Configure — provide a shell command template with
{key}placeholder
If configure, prompt for the template. Examples to show: jira issue view {key} --plain, linear issue {key}, gh issue view {key} --repo owner/repo.
Store as ticket_cli_fetch. Empty string if skipped.
Step 3: Verification commands
These are the shell commands the implementor runs at the end of Act as the final quality gate. They need to cover the full CI surface for the kinds of changes ioda will drive — a too-narrow list means the implementor ships a feature the implementor thinks is green but CI rejects. See ${CLAUDE_PLUGIN_ROOT}/references/verification-commands.md for the full authoring guide; the Step runs a monorepo check so first-time configuration lands on a coverage-aware shape, not a workspace-scoped gap.
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.
- 10d ago First seen · 127 lines · 28 tokens per session scan A 5ced2a98f9da
ioda-init is a skill published in the GitHub repository luis-at-safebase/luism-claude-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,283 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.