Borrowing it
Nothing to install: this file belongs to greenpau/go-authcrunch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/greenpau/go-authcrunch/main/.codex/skills/testing-and-ci/SKILL.mdgit clone --depth 1 https://github.com/greenpau/go-authcrunchWrote 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/greenpau/go-authcrunch/testing-and-ci)<a href="https://agentmods.dev/skills/greenpau/go-authcrunch/testing-and-ci"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/testing-and-ci/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/greenpau/go-authcrunch/testing-and-ci"><img src="https://agentmods.dev/badge/skills/greenpau/go-authcrunch/testing-and-ci.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.00056 | $0.03702 |
| Opus 5 | $0.00028 | $0.01851 |
| Sonnet 5 | $0.00011 | $0.00740 |
| Haiku 4.5 | $0.00006 | $0.00370 |
Grade A, and why
testing-and-ci 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 yesterday.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing and CI
Corresponding Tests
Every Go code change must have corresponding automated tests. Identify the tests that exercise each changed behavior or contract before marking the work complete. This applies to library code, CLI code, internal helpers, configuration, serialization, and refactors; a small change is not a reason to omit coverage.
Add or update tests in the same change when adding or changing behavior. Cover the intended result and meaningful error or boundary cases. Bug fixes require a regression test that demonstrates the defect and passes with the fix. For package extraction or rewiring, cover both the reusable API and the caller integration.
For changes that preserve behavior, identify and run existing tests that directly exercise the affected contract, adding coverage wherever it is missing. Do not add redundant tests solely to produce a test-file diff. For test-helper or test-only changes, run the tests that use the changed code.
Assertions must verify observable behavior or invariants rather than mirror the implementation. A successful build, lint check, unrelated test run, or aggregate coverage percentage does not establish corresponding test coverage. Run the relevant tests through the lifecycle below and report the commands and results. If execution is blocked, report the exact blocker and the tests left unverified; do not claim validation passed.
Required End-to-End Coverage
Whenever developing tests, also add or extend E2E tests for the affected behavior in the same change. This includes test-only work, regression tests, and changes to test helpers. Run the E2E cases before marking the work complete; unit tests, handler recorders, and coverage percentages alone do not satisfy this requirement.
Exercise the supported consumer entry point through the real production components to an observable result. For portal HTTP features, use a local TLS listener, a temporary identity database, real login and authorization, and a client that cannot access portal internals. For CLI behavior, run the built executable. For library or automation behavior, exercise the owning public workflow with real temporary files or local processes as appropriate.
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.
- yesterday First seen · 331 lines · 56 tokens per session scan A 55b61f4f9438
testing-and-ci is a skill published in the GitHub repository greenpau/go-authcrunch (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 3,702 once invoked, about $0.0003 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-09-13.
Other skills, from other repositories
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...
checkly
Expert guidance for Checkly, the synthetic monitoring platform that runs Playwright-based browser checks and API checks from locations worldwide. Helps developers implement monitoring-as-code (MaC) with the Checkly CLI, set up API and browser checks, configure alerting, and integrate monitoring into CI/CD pipelines.
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.