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 ondrej-svec/heart-of-gold-toolkit --skill workgit clone --depth 1 https://github.com/ondrej-svec/heart-of-gold-toolkitWrote 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/ondrej-svec/heart-of-gold-toolkit/work)<a href="https://agentmods.dev/skills/ondrej-svec/heart-of-gold-toolkit/work"><img src="https://agentmods.dev/badge/skills/ondrej-svec/heart-of-gold-toolkit/work/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/ondrej-svec/heart-of-gold-toolkit/work"><img src="https://agentmods.dev/badge/skills/ondrej-svec/heart-of-gold-toolkit/work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.02305 |
| Opus 5 | $0.00036 | $0.01153 |
| Sonnet 5 | $0.00014 | $0.00461 |
| Haiku 4.5 | $0.00007 | $0.00231 |
Grade A, and why
work 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work
Execute a plan and ship it. This is the ONLY skill that writes code. Read tasks, implement in dependency order, test after every change, commit incrementally, quality checks, push.
Boundaries
This skill MAY: read code, write code, edit files, run tests, run linters, commit, push, create PRs.
This skill MAY NOT: skip the plan, skip tests, ship with known failures, commit .env or secrets.
This skill requires a plan. If no plan exists, suggest /deep-thought:plan first. Don't improvise implementation from scratch.
Common Rationalizations
| Shortcut | Why It Fails | The Cost |
|---|---|---|
| "Skip reading the plan — I'll figure it out" | The plan has context, decisions, and dependencies you'll miss | Build the wrong thing → rework |
| "Giant commits — I'll sort it out later" | Hard to review, hard to revert, hide bugs | Technical debt + review burden |
| "Tests at the end — I'm in flow" | Late testing finds problems when fixing them is most expensive | Cascading failures |
| "Ship without quality checks — small change" | Small changes touch auth, data, or boundaries more often than you think | Bug in production from a "safe" change |
Phase 0: Load the Plan
Entry: User invoked /work with a plan path or no arguments.
If invoked with a plan path:
- Read the plan completely
- Identify: tasks (checkboxes), dependencies, acceptance criteria
If invoked without a path:
- Check
docs/plans/(or project override path) for the most recent active plan (status: approvedorstatus: in_progressin frontmatter) - If one found: Ask the user whether to start that plan or choose a different one.
- If multiple found: Ask the user which plan to use.
- If none found: Ask whether to create a
/deep-thought:planfirst or describe what to build.
Prefer the harness's structured choice UI when available. Otherwise present concise numbered options in plain text.
If anything in the plan is unclear: Ask clarifying questions now — better to ask than build wrong.
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 · 264 lines · 71 tokens per session scan A ac369a93c0de
work is a skill published in the GitHub repository ondrej-svec/heart-of-gold-toolkit (19 stars, last pushed 21d ago), licensed MIT. It adds 71 tokens to every session and 2,305 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.