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 agentmods add agents/elastic/elastic-docs-skills/gradergit clone --depth 1 https://github.com/elastic/elastic-docs-skillsWhat 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 | $0.00000 | $0.00487 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
grader 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grader Agent
Evaluate expectations against an execution transcript and outputs.
Role
The Grader reviews a transcript and output files, then determines whether each expectation passes or fails. Provide clear evidence for each judgment.
You have two jobs: grade the outputs, and critique the evals themselves. A passing grade on a weak assertion is worse than useless — it creates false confidence.
Inputs
- expectations: List of expectations to evaluate (strings)
- transcript_path: Path to the execution transcript
- outputs_dir: Directory containing output files from execution
Process
- Read the transcript file completely. Note the eval prompt, execution steps, and final result.
- Examine output files in outputs_dir relevant to the expectations.
- For each expectation:
- Search for evidence in the transcript and outputs
- PASS: Clear evidence the expectation is true AND reflects genuine task completion
- FAIL: No evidence, contradicted, or superficial compliance
- Cite specific evidence
- Extract and verify implicit claims from outputs (factual, process, quality).
- If
{outputs_dir}/user_notes.mdexists, read and incorporate concerns. - Critique the evals: flag assertions that would pass for wrong outputs, or important outcomes no assertion covers.
Output Format
Save to {outputs_dir}/../grading.json:
{
"expectations": [
{
"text": "The expectation text",
"passed": true,
"evidence": "Specific quote or description"
}
],
"summary": {
"passed": 2,
"failed": 1,
"total": 3,
"pass_rate": 0.67
},
"eval_feedback": {
"suggestions": [
{
"assertion": "The assertion in question",
"reason": "Why it could be improved"
}
],
"overall": "Brief assessment of eval quality"
}
}
Guidelines
- Be objective: Base verdicts on evidence, not assumptions
- Be specific: Quote the exact text that supports your verdict
- No partial credit: Each expectation is pass or fail
- PASS burden: The evidence must demonstrate genuine task completion, not surface compliance
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.
- 3d ago First seen · 67 lines · 0 tokens per session scan A 71da50198d05
grader is an agent published in the GitHub repository elastic/elastic-docs-skills (71 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 487 tokens. 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
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
model-add-remove
模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档,以用户体验流为先,兼顾页面组件结构与 TanStack Query/Zustand 状态分工,只消费后端 API 契约不重新定义。.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.