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/griddynamics/rosetta/checklistnpx skills add griddynamics/rosetta --skill checklistgit clone --depth 1 https://github.com/griddynamics/rosettaWhat 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 | $0.00010 | $0.00493 |
| Opus 5 | $0.00005 | $0.00246 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
checklist 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 2d 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
Problem: Long-running work may drift, forget requirements, or falsely appear complete.
Solution: Create and maintain a checklist as the persistent completion spine.
-
After discovery/questions are resolved and before implementation, create a category/aspect-based checklist.
- Capture source of truth: requirements, acceptance criteria, constraints, non-goals, assumptions, and authoritative references.
- Cover all relevant internal/external factors.
- Categories/aspects must be cumulatively exhaustive; items mutually exclusive where practical.
- Include only medium+ findings.
- Calibrate severity from impact, risk, and consequences of omission/failure.
- Create before implementation context biases the analysis.
- Each item contains < 8 words
- Each item covers archetype/concept
- Checklist is not a plan
- Checklist has items for result verification
-
Store the checklist in a project/feature temporary location. It may be committed for multi-session work.
- Persist its path and validation instructions through context compaction.
-
Keep the checklist synchronized with scope.
- Add requirements, constraints, dependencies, or risks discovered later.
- Never silently delete, weaken, merge away, or downgrade existing items. Record the reason for any material change.
-
Before reporting completion, reload the checklist and validate every item against the final state.
- Resolve deviations, then repeat validation.
- Continue until the implementing agent finds zero unresolved medium+ issues.
-
Then spawn a fresh-eye reviewer subagent.
- Do not prime it with the implementing agent's conclusion.
- Give it the source of truth, checklist, relevant final state/diff, and validation evidence.
- It must independently assess:
- checklist completeness;
- actual satisfaction of every checklist item;
- missing medium+ risks based on impact/severity/consequences.
- It must report findings plus a 0–100% confidence score that the work is complete.
- Any new medium+ finding must be added to the checklist, resolved, and the validation cycle repeated.
-
Terminate successfully only when:
- implementing agent: zero unresolved medium+ findings;
- fresh-eye reviewer: zero unresolved medium+ findings;
- fresh-eye reviewer provides its final confidence score. Otherwise continue the cycle or explicitly report unresolved/blocked items instead of declaring completion.
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.
- 2d ago First seen · 47 lines · 10 tokens per session scan A 2cb85d99cfb7
checklist is a skill published in the GitHub repository griddynamics/rosetta (341 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 493 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
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
signing-entitlements
Inspect signing, entitlements, hardened runtime, and Gatekeeper issues for macOS apps. Use when asked to diagnose code signing failures, missing entitlements, sandbox problems, notarization prerequisites, or trust-policy launch errors.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
macos-test-triage
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…