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 Stijnman/grok-custom-skills --skill auto-testergit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/auto-tester)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/auto-tester"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/auto-tester/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/stijnman/grok-custom-skills/auto-tester"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/auto-tester.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.00032 | $0.00337 |
| Opus 5 | $0.00016 | $0.00169 |
| Sonnet 5 | $0.00006 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
auto-tester 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 11d 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
Auto Tester
When to Use
- User says run tests or task matches this capability
- User says auto test or task matches this capability
- User says validate changes or task matches this capability
- User says check tests or task matches this capability
Workflow
- Detect project type (Python, Node, skill-only).
- Run appropriate test command (pytest, npm test, or skill checklist).
- Parse results; classify pass/fail/flaky.
- On fail: invoke self-healing-error-recovery or report with fix hints.
Integrations
goal-verifierself-healing-error-recoveryhyper-skill-tester
Error Handling
| Failure | Response |
|---|---|
| No test suite | Run smoke checks: import, lint, dry-run. |
Gotchas
- Never skip tests before marking goal-verifier complete.
Example
Input: User request matching triggers above. Output: Structured result per workflow with integrations invoked as needed.
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.
- 11d ago First seen · 48 lines · 32 tokens per session scan A b0a74f6ce4f7
auto-tester is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 337 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
promptfoo-redteam-setup
Create or refine promptfoo redteam setup configs: purpose, targets, plugins, strategies, frameworks, multi-input target inputs, policy text, grader guidance, contexts, and static-code-derived target/threat mapping. Use when preparing a red team scan plan from live probes, code evidence, or provider configs, or when…
promptfoo-provider-setup
Configure promptfoo providers or redteam targets for hosted models, live HTTP APIs, Python/JavaScript local scripts, agent SDKs, or multi-input systems. Use when connecting promptfoo to the system under test, mapping vars, auth env vars, request bodies, response transforms, or static-code-derived provider wrappers. Do…
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.