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 hyhmrright/logic-lens --skill new-skillgit clone --depth 1 https://github.com/hyhmrright/logic-lensWrote 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/hyhmrright/logic-lens/new-skill)<a href="https://agentmods.dev/skills/hyhmrright/logic-lens/new-skill"><img src="https://agentmods.dev/badge/skills/hyhmrright/logic-lens/new-skill/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/hyhmrright/logic-lens/new-skill"><img src="https://agentmods.dev/badge/skills/hyhmrright/logic-lens/new-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00050 | $0.00619 |
| Opus 5.5 | $0.00020 | $0.00248 |
| Sonnet 5.5 | $0.00010 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
new-skill 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 1mo 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
new-skill
CLAUDE.md → "Adding a New Skill" is the authoritative checklist. This skill exists to make sure every step actually runs — the session-start loop and the eval cases are the ones most often forgotten.
Read CLAUDE.md's "Adding a New Skill" section now, then execute its steps for logic-<NAME> (ask the user for <NAME> if not in $ARGUMENTS):
skills/logic-<NAME>/SKILL.md— copy the frontmatter shape fromskills/logic-review/SKILL.md(name+description). ThedescriptionMUST include a "Do NOT trigger for:" clause and a "SCOPE … RULE" line distinguishing it from the other skills. Process section = 5–7 numbered items, each citing a guide step. Follow lazy-loading perskills/_shared/common.md§13.skills/logic-<NAME>/logic-<NAME>-guide.md— numbered steps (Step 1, 2, …), each explaining the why, concrete examples over abstractions.commands/logic-<NAME>.md— mirrorcommands/logic-review.md:--- description: <one line> allowed-tools: Skill --- Use the Skill tool to invoke `logic-lens:logic-<NAME>`, then follow its instructions exactly. $ARGUMENTShooks/session-start(CLAUDE.md step 6 — easy to miss) — addlogic-<NAME>to BOTH thefor skill in …loop and the printed skill list:grep -n "for skill in" hooks/session-start- Eval cases (CLAUDE.md step 7 — easy to miss) — add 3–5 content cases to
evals/content/v2/evals-v2.json. Trigger cases underevals/trigger/v2/are optional and only catch description regressions (positive cases always score 0% — see CLAUDE.md → Gotchas). gemini-extension.json— CLAUDE.md says Gemini auto-discovers fromskills/, but the file also enumerates each skill+command undercontribution. If you want that list complete, addlogic-<NAME>entries to bothcontribution.skillsandcontribution.commands. (Not checked byvalidate-repo.sh.)- Validate — run
npm run validateand confirm all checks pass.
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.
- 1mo ago First seen · 30 lines · 50 tokens per session scan A 65b85244b89f
new-skill is a skill published in the GitHub repository hyhmrright/logic-lens (25 stars, last pushed 24d ago), licensed MIT. It adds 50 tokens to every session and 619 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-08-30.
Other skills, from other repositories
river-review-code
A general code-review skill that checks readability, maintainability, and type safety, with routing for several specialized checks.
Standard Review Policy for Midstream
Applies standard AI review policy guidelines for midstream (implementation) phase reviews.
review-loop
Run a bounded cross-model peer review and fix loop, or report findings in read-only mode.
harness
Plan or execute complex tasks through the harness checkpoint, evaluation, and retro workflow.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.