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.
git clone --depth 1 https://github.com/squerne/open-career-skillsWrote 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/commands/squerne/open-career-skills/mine-evidence)<a href="https://agentmods.dev/commands/squerne/open-career-skills/mine-evidence"><img src="https://agentmods.dev/badge/commands/squerne/open-career-skills/mine-evidence/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/commands/squerne/open-career-skills/mine-evidence"><img src="https://agentmods.dev/badge/commands/squerne/open-career-skills/mine-evidence.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.00019 | $0.00195 |
| Opus 5 | $0.00010 | $0.00097 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
mine-evidence 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 11d 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.
What it actually says
Use the evidence-miner skill (.claude/skills/evidence-miner/SKILL.md) exactly as written.
- $ARGUMENTS (if provided) are the repo/folder paths to mine; otherwise ask.
- Use the bash tool to execute the skill's read-only
git log/git shortlog/gh pr listcommands directly; do not ask for permission for read-only git/gh commands. Never run write commands. - Groundedness rule is absolute: no citable artifact, no proposed achievement; business impact numbers come from the user, never inferred from code.
- Confirmed stories are filed to
story-bank/via thestar-story-extractorskill, with an## Evidencesection.
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.
- 11d ago First seen · 12 lines · 19 tokens per session scan A 179f3c891cfe
mine-evidence is a command published in the GitHub repository squerne/open-career-skills (22 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 195 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-30.
Other commands, from other repositories
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
prepare-release
Release readiness review with project-steward (commits, version sync, changelog, updater).
reconcile
Establish git ground truth (branch, status, stashes, worktrees, ahead/behind) before any mutation, halt on protected or destructive operations, then carry the known-good state through a single-concern commit, a push, an open PR, and — after the PR merges — a fast-forward of the default branch. Enforces Law 1 (Research…
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
dream-apply
Walk a dream proposal artifact, review each item, apply accepted ones, commit.