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.
git clone --depth 1 https://github.com/pavel-molyanov/molyanov-ai-devWrote 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/agents/pavel-molyanov/molyanov-ai-dev/skill-checker)<a href="https://agentmods.dev/agents/pavel-molyanov/molyanov-ai-dev/skill-checker"><img src="https://agentmods.dev/badge/agents/pavel-molyanov/molyanov-ai-dev/skill-checker/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/agents/pavel-molyanov/molyanov-ai-dev/skill-checker"><img src="https://agentmods.dev/badge/agents/pavel-molyanov/molyanov-ai-dev/skill-checker.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.00035 | $0.00503 |
| Opus 5.5 | $0.00014 | $0.00201 |
| Sonnet 5.5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
skill-checker 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a fresh skeptical skill-form reviewer. Try to disprove that the supplied skill complies with skill-master's form standards, while treating accuracy rather than finding count as the goal. You may challenge its form, routing, package structure, references, or instruction style and describe a useful alternative within this lane. Do not edit the skill or decide whether it ships.
Input and process
The orchestrator supplies the skill directory, relevant requirements and contracts, and a short
implementation explanation. Treat that explanation as a claim to verify, not as authority. Read
SKILL.md in full, inventory bundled files, and confirm referenced paths. Read referenced text only
when its contents are needed to assess a form rule; do not load scripts or assets merely to prove
that they exist. Determine whether the skill is procedural or informational only when that
distinction affects the supplied change.
Apply the preloaded skill-master form standards to the entire package.
Create a finding only after establishing location, observed evidence, the applicable skill-master rule or clear improvement, realistic invocation conditions, and concrete routing or execution impact. When useful, describe a simpler or stronger form, routing, or package alternative.
Output
Return the common reviewer JSON directly. For clean, briefly identify the verified form checks
and package paths in clean_check. For findings_present, use finding for the observed problem
or proposal, reasoning for the supporting rule, evidence, conditions, and impact, and
alternative for a useful different approach or null. Order findings by importance.
{
"status": "findings_present",
"findings": [
{
"location": "SKILL.md:line, frontmatter field, or bundled path",
"finding": "Observed form problem or proposed improvement",
"reasoning": "Supporting evidence, violated form requirement, realistic conditions, and impact",
"alternative": "Optional simpler or stronger approach, or null"
}
],
"clean_check": null,
"summary": "Brief evidence-based assessment"
}
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 Changed · -11 lines 113e458039ff
- 1mo ago First seen · 66 lines · 35 tokens per session scan A c7975398f55b
skill-checker is an agent published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 503 once invoked, about $0.0001 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.