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 dmae97/omk --skill automate-megit clone --depth 1 https://github.com/dmae97/omkWrote 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/dmae97/omk/automate-me)<a href="https://agentmods.dev/skills/dmae97/omk/automate-me"><img src="https://agentmods.dev/badge/skills/dmae97/omk/automate-me/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/dmae97/omk/automate-me"><img src="https://agentmods.dev/badge/skills/dmae97/omk/automate-me.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.00073 | $0.01782 |
| Opus 5.5 | $0.00029 | $0.00713 |
| Sonnet 5.5 | $0.00015 | $0.00356 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
pstack-automate-me 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automate me
A guided flow for turning the user's working conventions into a skill agents will follow. The output is one -mode skill tailored to them (e.g. jay-mode, priya-mode).
This skill orchestrates three others: an inline mining pass (see step 1), your harness's skill-authoring skill (authoring), and the unslop skill (prose discipline). It sequences them. It doesn't replace them.
The skill-authoring skill is an installed skill-creator skill when present, otherwise the Agent Skills format at agentskills.io. "create-skill" below means whichever of these you use.
Flow
0. Check for an existing skill
Look recursively for *-mode/SKILL.md matching the user's handle in your harness's skill folders. In the project: .omk/skills/. For the user: ~/.omk/agent/skills/. Mode skills can live in a personal category directory (<skills>/<handle>/), not only at the top level. If one exists, confirm intent with your structured-question tool (in OMK, ask in chat with numbered options) unless they already said "update my skill" or similar:
- Update the existing skill (default for repeat runs)
- Start fresh (rare, ask why before doing it)
Update mode changes the rest of the flow:
- Step 1 mines only history since the skill was last edited (
git log -1 --format=%cI <path>). - Step 2 asks what's changed or missing, not what to capture from zero.
- Step 4 edits the existing file in place. Preserve sections the user hasn't contradicted. Revise ones with new evidence. Add new sections only for genuinely new rules.
1. Mine their history
Locate the active workspace's transcripts before fanning out. Use only that workspace's directory. Don't glob across every project's directory. That crosses workspace boundaries and reads private chats from unrelated projects. In OMK they live in the active workspace's session directory:
~/.omk/agent/sessions/--<slug>--/*.jsonl, where<slug>is the workspace path with the leading slash dropped and each "/" turned into "-".- Keep only sessions whose recorded cwd is this workspace; never read another project's sessions.
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 Changed · -3 lines 97ad633e796c
- yesterday First seen · 112 lines · 73 tokens per session scan A 4c3d724788b8
pstack-automate-me is a skill published in the GitHub repository dmae97/omk (151 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,782 once invoked, about $0.0003 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-27.
Other skills, from other repositories
cool-workflow
Use when the user asks for Cool Workflow, CW, agent workflow control-plane, TypeScript workflow orchestration, phased multi-agent work, background workflow tasks, reusable workflow apps, or auditable agent run state.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
loop
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
gmail
Search, read, draft, and send Gmail when the user asks to work with their inbox or email.
google-calendar
Read schedules, check availability, and create or update Google Calendar events when the user asks to work with their calendar.