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 zahardev/aicontext --skill gh-fix-testsgit clone --depth 1 https://github.com/zahardev/aicontextWrote 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/zahardev/aicontext/gh-fix-tests)<a href="https://agentmods.dev/skills/zahardev/aicontext/gh-fix-tests"><img src="https://agentmods.dev/badge/skills/zahardev/aicontext/gh-fix-tests/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/zahardev/aicontext/gh-fix-tests"><img src="https://agentmods.dev/badge/skills/zahardev/aicontext/gh-fix-tests.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.00015 | $0.00037 |
| Opus 5.5 | $0.00006 | $0.00015 |
| Sonnet 5.5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
gh-fix-tests 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
Read and follow .aicontext/prompts/gh-fix-tests.md
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 Changed · -34 tokens per session c15f05bfb1f9
- 1mo ago First seen · 7 lines · 49 tokens per session scan A 8b028fb2b066
gh-fix-tests is a skill published in the GitHub repository zahardev/aicontext (2 stars, last pushed 26d ago), licensed MIT. It adds 15 tokens to every session and 37 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-31.
Other skills, from other repositories
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.