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 automagik-dev/genie/plugin install mikroWrote 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/automagik-dev/genie/microagent-create)<a href="https://agentmods.dev/skills/automagik-dev/genie/microagent-create"><img src="https://agentmods.dev/badge/skills/automagik-dev/genie/microagent-create/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/automagik-dev/genie/microagent-create"><img src="https://agentmods.dev/badge/skills/automagik-dev/genie/microagent-create.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.00194 | $0.02638 |
| Opus 5.5 | $0.00078 | $0.01055 |
| Sonnet 5.5 | $0.00039 | $0.00528 |
| Haiku 4.5 | $0.00019 | $0.00264 |
Grade A, and why
microagent-create 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 today.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposing an mikro microagent from real usage
The contract, first
You measure, you draft, you stop. The draft goes into
.mikro/agents/<name>.proposed/ and nowhere else. You do not rename it, you do
not copy it somewhere it would load, and you do not offer to. The rename is the
user's, and it is the entire approval step.
The boundary is mechanical, not a promise: discoverAgents skips any directory
whose name ends .proposed, case-insensitively
(src/mcp/agents.ts — isProposedDir, applied in the discovery loop). Because
tools/call dispatches from the same scan that builds tools/list
(src/mcp/server.ts:252, src/mcp/server.ts:771), a draft is neither listed
nor callable; calling it by its would-be name answers Unknown tool: mikro_<name>_proposed. Renaming publishes it on the next request, without a
reconnect. tests/mcp-agents.test.ts pins all of that.
Two consequences worth stating to the user:
.proposedis reserved. An agent legitimately namedfoo.proposedwould be permanently invisible. The skip's error surface is silence by design, so say so rather than letting them find out.- Nothing you write is live. Do not describe the draft as "installed", "created", or "ready to use". It is a proposal on disk.
Step 1 — measure, do not read
Run the bundled scanner. Do not open transcripts yourself: on an active host they are ~100 MB a day, and reading them into this session to find out what is filling this session would be the joke telling itself.
node "${CLAUDE_PLUGIN_ROOT}/skills/microagent-create/scan-transcripts.mjs" --hours 24
It streams ~/.claude/projects/**/*.jsonl and returns about a page: every tool
call bucketed into an offload family, ranked by the context that family's
results returned. Useful flags: --hours N (widen a quiet window),
--min-calls N (default 5), --project <substring>, --json, and
--explain <family> --examples N for the per-call drill-down with
transcript:line references.
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.
- today First seen · 199 lines · 194 tokens per session scan A 592a7198dcff
microagent-create is a skill published in the GitHub repository automagik-dev/genie (346 stars, last pushed today), licensed MIT. It adds 194 tokens to every session and 2,638 once invoked, about $0.0008 per session on Opus 5.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-10-16.
Other skills, from other repositories
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
static
Stash is your personal home for agent work. Everything you create is scoped to your account — it is yours alone, with nothing to pick or set up first. Your Stash has three primary surfaces.
brief
Brief the user on what they saved in a period — the thread running through it, not a list.
resurface
Pick a few old saves worth revisiting now, and say why now.
cleanup
Find duplicates, dead links and untagged items in a saved library and propose what to do about each.