Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mgechev/skillgradenpx agentmods add skills/mgechev/skillgrade/skillgrade-gradersWrote 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/mgechev/skillgrade/skillgrade-graders)<a href="https://agentmods.dev/skills/mgechev/skillgrade/skillgrade-graders"><img src="https://agentmods.dev/badge/skills/mgechev/skillgrade/skillgrade-graders/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/mgechev/skillgrade/skillgrade-graders"><img src="https://agentmods.dev/badge/skills/mgechev/skillgrade/skillgrade-graders.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.01477 |
| Opus 5.5 | $0.00025 | $0.00591 |
| Sonnet 5.5 | $0.00013 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
skillgrade-graders 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 13d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillgrade Grader Authoring
Procedures
Step 1: Identify the Grading Strategy
- Determine which grader types the task needs:
- Deterministic: objective verification — file checks, output comparison, test execution.
- LLM rubric: qualitative assessment — workflow compliance, code quality, reasoning.
- Human: subjective judgment — design fidelity, UX, documentation clarity.
- For most tasks, combine deterministic (weight 0.7) and LLM rubric (weight 0.3).
- Add a human grader when automated checks can't reliably measure quality.
Step 2: Write a Deterministic Grader
- Create a script in the skill's
graders/directory (bash or TypeScript). - The script must output a JSON object to stdout with the following structure:
{"score": 0.67, "details": "2/3 checks passed", "checks": [{"name": "check-name", "passed": true, "message": "Description"}]} score(0.0–1.0) anddetailsare required.checksis optional but recommended.- Read
references/grader-output-schema.mdfor the full output specification. - Use
awkfor arithmetic in bash scripts —bcis not available innode:20-slim. - Access task context via
SKILLGRADE_INPUTenv var (JSON withtask,trial,expected,metadata). - Reference the grader in eval.yaml:
- type: deterministic run: bash graders/check.sh weight: 0.7
Step 3: Write an LLM Rubric Grader
- Draft a rubric with explicit scoring criteria and point allocations.
- Structure the rubric into weighted sections that sum to 1.0:
Workflow Compliance (0-0.5): - Did the agent follow the mandatory workflow steps? Efficiency (0-0.5): - Completed in ≤5 commands without trial-and-error? - Reference the rubric in eval.yaml:
- type: llm_rubric rubric: | [rubric text or file path] weight: 0.3 provider: gemini # optional: gemini (default) | anthropic | openai model: gemini-3.5-flash # optional model override (defaults to the latest dynamically resolved flash model) - For long rubrics, store in a separate file and reference by path:
rubric: rubrics/quality.md.
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.
- 13d ago Changed · +39 lines · +9 tokens per session a8745ac2a241
- 1mo ago First seen · 77 lines · 54 tokens per session scan A c6f047ca9b5f
skillgrade-graders is a skill published in the GitHub repository mgechev/skillgrade (731 stars, last pushed 14d ago), licensed MIT. It adds 63 tokens to every session and 1,477 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-08-30.
Other skills, from other repositories
rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.
testing-strategy
Design a test suite for an open-source project that contributors can actually run and trust. Use when a project has no tests, when the suite is slow or flaky, when deciding what to test and at what level, when setting a coverage policy, or when contributors' PRs keep failing CI for unrelated reasons. Covers the test…
fix-failing-tests
Iteratively fix all failing tests until the test suite is green.
Swift Testing
Modern Swift Testing framework patterns and best practices.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
quality-architect
Designs automated API tests (Postman), load tests (K6), and mockup responses.