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 frankxai/claude-skills-library --skill santa-methodgit clone --depth 1 https://github.com/frankxai/claude-skills-libraryWrote 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/frankxai/claude-skills-library/santa-method)<a href="https://agentmods.dev/skills/frankxai/claude-skills-library/santa-method"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/santa-method/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/frankxai/claude-skills-library/santa-method"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/santa-method.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.00045 | $0.00413 |
| Opus 5.5 | $0.00018 | $0.00165 |
| Sonnet 5.5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
santa-method 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 8d 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
Two reviewers, then stop
The author does not grade the work. Two other readers use the same rubric. Neither sees the other's notes until both have answered.
Order
- Run the deterministic checks first: build, types, tests. This pass is for behavior, claims, and omissions.
- Give both reviewers the spec and the diff. Ask for a pass or a fail per criterion, with a file or a line. A pass that cites nothing is not a pass.
- Ship only when both pass. If either fails, fix the cited items and ask again with fresh readers.
- Stop after three rounds. The remaining list goes to a person. A pass with an empty citation is a fail. The round counter is
node absorbed/harness/santa-round.mjs.
Estate gates that sit on top
- The author harness does not sign its own pull request. Open a draft.
- Frank's inspection is not the quality layer. A second provider still reads a public or priced artifact.
- Do not merge from the chair that wrote the change.
Rubric, minimum
- The claim matches a file, a command, or a page you can open.
- The change does what the task asked, including the edge the task named.
- No secret, no invented metric, no second coordinator smuggled in as a helper.
Where this came from
The two-reviewer loop follows affaan-m/ECC skills/santa-method at 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 (MIT). The three-round cap, the draft-PR rule, and the ban on self-signoff are estate law.
Built on SIP.
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.
- 8d ago Changed bc1d82cd7f01
- 9d ago First seen · 35 lines · 45 tokens per session scan A e82dddf7bb30
santa-method is a skill published in the GitHub repository frankxai/claude-skills-library (47 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 413 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-10-11.
Other skills, from other repositories
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
pr
A writing guide for creating pull request descriptions, which explain a proposed code change to reviewers. It uses sections for the summary, evidence, merge risk, and the likely area affected by the change.
code-review
A code-review skill that compares changes from a chosen commit, branch, tag, or merge-base against the repository’s coding standards and the related issue or specification.
improve-codebase-architecture
A skill that scans a codebase for places where restructuring could make future changes and testing easier, then produces an HTML report for selected improvements.
andrej-karpathy
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
code-reviewer
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.