Borrowing it
Nothing to install: this file belongs to centry-digital/bukku. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/centry-digital/bukku/main/.claude/skills/verify-bukku/SKILL.mdgit clone --depth 1 https://github.com/centry-digital/bukkuWrote 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/centry-digital/bukku/verify-bukku)<a href="https://agentmods.dev/skills/centry-digital/bukku/verify-bukku"><img src="https://agentmods.dev/badge/skills/centry-digital/bukku/verify-bukku/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/centry-digital/bukku/verify-bukku"><img src="https://agentmods.dev/badge/skills/centry-digital/bukku/verify-bukku.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.00111 | $0.01746 |
| Opus 5.5 | $0.00044 | $0.00698 |
| Sonnet 5.5 | $0.00022 | $0.00349 |
| Haiku 4.5 | $0.00011 | $0.00175 |
Grade A, and why
verify-bukku 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 7d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify bukku
The product has two surfaces, both thin layers over packages/core and the Bukku REST API at https://api.bukku.my (hard-coded, no local stand-in):
- CLI
bukku(packages/cli, published as@centry-digital/bukku-cli). Short-lived: one process per command, JSON on stdout, a JSON error and a non-zero exit code on failure. Credentials come from--api-token/--company-subdomain, thenBUKKU_API_TOKEN/BUKKU_COMPANY_SUBDOMAIN, then~/.bukkurc. - MCP server
bukku-mcp(packages/mcp, published as@centry-digital/bukku-mcp). Spoken to over stdio by an AI client. It needs both env vars and calls the API to validate the token before it lists any tools, so without real credentials only its startup error can be driven.
All helpers live in .claude/skills/verify-bukku/scripts/. Run them from the repo root. Below, V=.claude/skills/verify-bukku.
Launch
Prerequisites: Node 22 (.nvmrc), npm ci done.
$V/scripts/verify.sh launch
- Runs
npm run build, creates a run id, an evidence folder.verify/evidence/<run id>/and a sandbox.verify/run/<run id>/holding a throwawayHOME(so~/.bukkurcis never the user's) andTMPDIR. - Ready when it prints
ready. The run id is saved in.verify/run/current; every other command uses it (orVERIFY_RUN_IDif set). - There is no server to keep alive: each
cliormcpdrive below is its own process. Runs don't share state, but only one run is "current" per checkout.
Live mode. By default every drive runs with no Bukku credentials in its environment. For a live drive, export BUKKU_API_TOKEN and BUKKU_COMPANY_SUBDOMAIN for a test company (never a client's books) and set VERIFY_LIVE=1. Even then the harness refuses any CLI write that lacks --dry-run and any MCP tool other than list-*, get-* and search-*, unless VERIFY_ALLOW_WRITES=1 is also set. Set that only when the repo owner has approved writes to that test company for this run. In live mode any HTTPS_PROXY, NO_PROXY and NODE_EXTRA_CA_CERTS are passed through to drives (with NODE_USE_ENV_PROXY=1, which Node's fetch needs to use a proxy).
What ships with it
10 files 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.
- features/api-write-rules.md 6.8 KB
- features/cli-credentials.md 2.6 KB
- features/cli-dry-run.md 2.4 KB
- features/cli-reads.md 2.7 KB
- features/journal-entry-validation.md 2.3 KB
- features/mcp-server.md 2.1 KB
- features/packaging.md 2.4 KB
- features/README.md 2.7 KB
- scripts/mcp-call.mjs 1.4 KB runs code
- scripts/verify.sh 7.1 KB runs code
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.
- 7d ago First seen · 88 lines · 111 tokens per session scan A cd77b6bf0bcb
verify-bukku is a skill published in the GitHub repository centry-digital/bukku (9 stars, last pushed 4d ago), licensed MIT. It adds 111 tokens to every session and 1,746 once invoked, about $0.0004 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-10-22.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.