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/ericlitman/open-pstack/automate-menpx skills add ericlitman/open-pstack --skill automate-megit clone --depth 1 https://github.com/ericlitman/open-pstackWrote 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/ericlitman/open-pstack/automate-me)<a href="https://agentmods.dev/skills/ericlitman/open-pstack/automate-me"><img src="https://agentmods.dev/badge/skills/ericlitman/open-pstack/automate-me.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.00072 | $0.01866 |
| Opus 5 | $0.00036 | $0.00933 |
| Sonnet 5 | $0.00014 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- automate-me — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 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), the plugin-dev:skill-development skill (authoring), and the unslop skill (prose discipline). It sequences them; it doesn't replace them.
Platform note. On Codex or another non-Claude runtime, the Claude tool names, claude-* slugs, and Claude built-in skills named below (including plugin-dev:skill-development) are Claude defaults. Resolve them via codex-tools.md.
Flow
0. Check for an existing skill
Look recursively for .claude/skills/**/*-mode/SKILL.md and ~/.claude/skills/*-mode/SKILL.md matching the user's handle. Mode skills can live in a personal category directory (.claude/skills/<handle>/), not only at the top level. If one exists, confirm intent with AskUserQuestion (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. Claude Code stores them at ~/.claude/projects/<encoded-cwd>/*.jsonl, where <encoded-cwd> is the workspace's working directory with / → -. Use only that path. Don't glob across ~/.claude/projects/. That crosses workspace boundaries and reads private chats from unrelated projects.
Survey recent agent conversations within that scope for recurring patterns. Run multiple parallel subagents across slices of history (e.g. last 2-4 weeks, split into 3 slices so each has enough material). Each slice mining subagent reads transcripts from the workspace-scoped path the parent provides, looks for the signals below, and returns a short structured list of patterns it saw with evidence pointers. Default signals worth hunting:
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 · 111 lines · 72 tokens per session scan A 0052c5502231
automate-me is a skill published in the GitHub repository ericlitman/open-pstack (206 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,866 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…