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 ANcpLua/ancplua-claude-plugins --skill implementgit clone --depth 1 https://github.com/ANcpLua/ancplua-claude-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/ancplua/ancplua-claude-plugins/implement)<a href="https://agentmods.dev/skills/ancplua/ancplua-claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/implement/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/ancplua/ancplua-claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/ancplua/ancplua-claude-plugins/implement.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.00064 | $0.00634 |
| Opus 5.5 | $0.00026 | $0.00254 |
| Sonnet 5.5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
implement 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 16d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nihil Implementation
Activate Implementation Mode. You may modify files inside the requested scope. A
PreToolUse hook blocks git push, git tag, package publishing, version bumps, and
obviously destructive shell while this mode is active — those are release steps; use
/nihil:release. git commit is allowed but not required.
Critical instructions
- Evidence before change. Implement only findings backed by repository evidence.
If a finding lacks evidence, do not implement it — go back to
/nihil:review. - Scope discipline. Modify only the files the task names or that the finding's evidence directly implicates. Do not perform broad refactors or opportunistic cleanup. Prefer three clear similar lines over a premature abstraction; extract only when repetition is real and the name improves understanding.
- Preserve behavior unless the task explicitly authorizes a behavior change.
Sequence
For each finding, follow:
Finding → Evidence → Change → Check
- Finding. State the finding and its evidence (files/symbols).
- Change. Make the minimal correct edit. Do not add error handling, fallbacks, guards, or validation for scenarios that cannot happen (proven only by source, types, framework guarantees, tests, or boundaries). Validate only at real boundaries. No feature flags, compatibility shims, or migration scaffolding when the correct fix is to change the code directly.
- Check. Run the relevant checks — build, tests, or run the artifact — and compare against a baseline you captured before editing. Do not report a failure you caused as preexisting.
Use specialized read-only agents (nihil:duplication-hunter,
nihil:abstraction-critic, nihil:boundary-reviewer, nihil:evidence-auditor) via
the Task tool to confirm a change is correct and in-scope when uncertain.
Output
Produce exactly this structure (the Stop hook blocks once if a Verification section is missing):
# Nihil Implementation
## Implemented Findings
<each finding implemented, with the evidence that justified it>
## Changed Files
<exact files changed and why>
## Verification
<checks you ran (build/tests/run), their output, and the baseline you compared to>
## Remaining Risks
<anything not fully verified, out-of-scope follow-ups, or assumptions made>
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.
- 16d ago First seen · 72 lines · 64 tokens per session scan A 87ddd92523b2
implement is a skill published in the GitHub repository ANcpLua/ancplua-claude-plugins (6 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 634 once invoked, about $0.0003 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-01.
Other skills, from other repositories
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
quality gates | code review debug audit security eval ui.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.