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/auravixstudio/caelo/check-worknpx skills add AuraVixStudio/caelo --skill check-workgit clone --depth 1 https://github.com/AuraVixStudio/caeloWrote 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/auravixstudio/caelo/check-work)<a href="https://agentmods.dev/skills/auravixstudio/caelo/check-work"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/check-work.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.00020 | $0.00313 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
Check work (verify against criteria) 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 6d 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
Check work (verify against criteria)
Use this after a change to confirm it actually meets the stated acceptance criteria,
combining a read-only reviewer with a tester that runs the suite in an isolated copy.
Steps
- Restate criteria. Write down the explicit acceptance criteria / definition of done for the change (ask the user if they are unclear).
- Review.
delegateareviewerto check the changes against each criterion and flag anything unmet, withfile:linereferences. - Test.
delegateatesterto run the relevant tests/build withrun_commandand report pass/fail with the actionable failures. - Decide. Report PASS only if the reviewer finds every criterion met AND the tester is green. Otherwise list exactly what fails.
- (Optional) Fix. If the user wants it closed out, hand the failures to the
implementloop; otherwise stop at the verdict.
Notes
- The reviewer is READONLY; the tester runs in an isolated worktree (its changes, if any, await merge review).
- Be explicit and binary in the final verdict — PASS or a concrete list of gaps.
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.
- 6d ago First seen · 30 lines · 20 tokens per session scan A bbff9a387cd4
Check work (verify against criteria) is a skill published in the GitHub repository AuraVixStudio/caelo (23 stars, last pushed 24d ago), licensed Apache-2.0. It adds 20 tokens to every session and 313 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 skills, from other repositories
skill-creator
Use when creating, updating, packaging, or validating an Lfcode skill. Covers user-managed and built-in bundled skills. 用户提到创建 Skill、更新 Skill、打包 Skill、校验 Skill 或技能规范时使用。.
tavern-management
Use when the user asks to import or translate an Lfcode Tavern or SillyTavern character card or worldbook, including PNG image cards, or manage the Tavern plugin lifecycle.
error-collection
记录已验证的工程错误、根因、错误模式和防复发验收规则，作为反面教材使用。.
playwright-browser
Use when controlling browser pages with Playwright MCP in Lfcode; guides navigation, screenshots, interaction, and reuse of hidden or collapsed embedded side browser targets instead of the Electron app shell.
contract-test-engineer
Use when the user asks to verify compatibility between an API provider and consumer, SDK and service, event producer and consumer, schema versions, or serialized data. Define and test the shared contract, including failures and compatibility rules, before changing either side.
e2e-test-engineer
Use when the user asks to create, improve, review, or repair end-to-end tests for a meaningful user workflow across the UI, runtime, backend, or installed application. Validate the real workflow at the highest useful boundary while keeping environments, accounts, and test data controlled.