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 DYZCODE/works-plugins --skill verify-public-commitgit clone --depth 1 https://github.com/DYZCODE/works-pluginsWrote 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/dyzcode/works-plugins/verify-public-commit)<a href="https://agentmods.dev/skills/dyzcode/works-plugins/verify-public-commit"><img src="https://agentmods.dev/badge/skills/dyzcode/works-plugins/verify-public-commit/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/dyzcode/works-plugins/verify-public-commit"><img src="https://agentmods.dev/badge/skills/dyzcode/works-plugins/verify-public-commit.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.00060 | $0.00513 |
| Opus 5.5 | $0.00024 | $0.00205 |
| Sonnet 5.5 | $0.00012 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
verify-public-commit 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 1mo 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
Verify Public Commit
Use works_verify_public_repository only when all of these are known:
- the repository is public and hosted at
https://github.com/<owner>/<repo>; - the exact work being judged is represented by a lowercase 40-character commit SHA;
- a supported WORKS contract matches the claim.
Before calling either WORKS tool, confirm all three eligibility conditions locally from the request. If any condition is absent or the requested claim is runtime, build, test, deployment, or broad production readiness, abstain without calling a WORKS tool. Do not use contract lint to decide basic eligibility.
After eligibility is established, call works_verify_public_repository
directly. Use node-package only for package structure, lockfile, and declared
automation. Use env-safety only for its exact environment-template contract.
Call works_public_contract_lint only when the user explicitly asks to inspect
contract metadata without verifying a repository.
Never substitute a branch, tag, pull request number, abbreviated SHA, mutable archive URL, private repository, or local working tree. Never create or push a commit merely to satisfy this skill.
The verification result includes a deterministic report. Return that report
verbatim and stop. Do not paraphrase it, add a heading, or manually reconstruct
the receipt. The first line labels the exact receipt status:
passed: every declared static outcome passed.failed: at least one declared outcome was disproved.blocked: WORKS could not collect complete evidence.error: the verifier failed.
Before returning the report, require trust.pinned_key_identity to be
matched and trust.key_id to equal
sha256:ccdae125f1c40606597f0111b484689b. A mismatch is a hard failure. This is
a pinned key-identity check, not independent signature validation.
The complete signed receipt remains in the tool's structured receipt field.
Do not inspect unrelated local files, reread the bundled key, rehash it with a
different convention, or call additional tools merely to restate the result.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 47 lines · 60 tokens per session scan A bd10c1b71843
verify-public-commit is a skill published in the GitHub repository DYZCODE/works-plugins (0 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 513 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
git-ai-search
Search and restore AI conversation context from git history.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.