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/boshu2/agentops/toil-miningnpx skills add boshu2/agentops --skill toil-mininggit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/toil-mining)<a href="https://agentmods.dev/skills/boshu2/agentops/toil-mining"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/toil-mining.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.1 | $0.00033 | $0.01415 |
| Opus 5 | $0.00016 | $0.00707 |
| Sonnet 5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
toil-mining 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 2d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Toil Mining — rank repeated friction
Mine explicitly supplied session, shell, RTK, or CASS history without modifying the sources. The result is evidence for a caller; this skill does not file work, schedule automation, or mutate a tracker.
Constraints
- Read-only over the supplied sources, because the skill gathers evidence and must never become a mutation lane.
- No work creation: it never files a tracker item, schedules automation, or names an owner, because those are caller decisions the evidence informs.
- Measured, not remembered: every count, cost, and error rate is read from the supplied history, so recency and salience cannot masquerade as frequency.
- Observations stay separate from recommendations, so a caller can re-weigh the ranking without inheriting an unstated conclusion.
Procedure
- Record the input sources, time window, filters, and query.
- Normalize repeated human actions while excluding documented machine echoes and generated repetitions. For caller-supplied Codex JSONL, use the deterministic helper below rather than an ad hoc transcript scan.
- Cluster equivalent actions and preserve representative evidence references.
- Score each cluster from measured frequency and observed pain such as elapsed time, failure count, interruption, or token cost.
- Emit a ranked report and stop.
Each candidate must contain a measured count, source references, confidence in the clustering, pain evidence, and the smallest plausible automation shape. Separate observations from recommendations.
Repetition threshold: measured, not remembered
A cluster qualifies as toil only above a measured floor: at least three occurrences in the supplied window, each resolvable to a source reference. Two occurrences are a coincidence; a vivid memory of "doing this constantly" with one resolvable instance is an anecdote. The named failure mode is salience mining — ranking by how annoying the last occurrence felt rather than by count, which surfaces yesterday's irritation over the quiet weekly drain. If the supplied history cannot establish the count, report the candidate as below-threshold with its actual measured count; never round an impression up to a frequency.
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.
- 2d ago First seen · 148 lines · 33 tokens per session scan A f11558f05d42
toil-mining is a skill published in the GitHub repository boshu2/agentops (433 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,415 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
askme
Explore intent with Verbalized Sampling before planning. Use when the task is ambiguous, you need maximum clarifying questions, or you want collaborative or adversarial mode via /askme.
slicing-code-context
Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Builds a deterministic slice packet and validates one constrained delegation. Not for source changes or broad repository exploration.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
autopilot
Run a hands-off plan-to-ship pipeline by chaining existing skills. Use when the user says "autopilot", "take this from plan to shipped", "run the whole pipeline", "hands-off ship it", or "do the end-to-end build".
llm-self-loop
Use when a button click, dashboard check, or human verdict sits inside an iteration loop. Replaces it with an autonomous gate or moves non-automatable work outside the loop. Don't use for remote, credential, publish, deploy, or irreversible changes.
plan-review-tune
Use when plan-mode enforcement hooks intercept a plan review or the user runs /plan-review-tune to tune which plan-review questions fire. Persists the tuned question flow to a local question-registry and hook configuration. Not for auditing a plan against code — use plan-review.