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 specsnl/agent-specs --skill ci-green-checkgit clone --depth 1 https://github.com/specsnl/agent-specsWrote 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/specsnl/agent-specs/ci-green-check)<a href="https://agentmods.dev/skills/specsnl/agent-specs/ci-green-check"><img src="https://agentmods.dev/badge/skills/specsnl/agent-specs/ci-green-check.svg" alt="Measured on agentmods" 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.00163 | $0.01475 |
| Opus 5 | $0.00081 | $0.00737 |
| Sonnet 5 | $0.00033 | $0.00295 |
| Haiku 4.5 | $0.00016 | $0.00147 |
Grade A, and why
ci-green-check 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 2d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Green Check
After every code change, discover and run all CI checks found in .github/ and get them green
before finishing.
Stack hand-off
This skill owns discovery, ordering, the fix loop, and reporting. The concrete commands depend on the stack:
- PHP / Laravel (a
composer.jsonexists at the repo root) → invoke thephp-checksskill for environment setup and the exact tool commands, then come back here for Steps 4–6. - Anything else → derive the commands from the Taskfile and the workflow steps you discovered in Step 1, following the runner rules in Step 3.
Step 1: Discover checks
1a. Check for a Taskfile first
ls Taskfile.yml Taskfile.yaml taskfile.yml taskfile.yaml 2>/dev/null
If a Taskfile exists, read it fully and extract:
- Setup tasks: anything that installs dependencies, prepares config, runs migrations, seeds —
common names:
setup,install,init,bootstrap - Check tasks: anything that runs tests or linters — common names:
checkall(the aggregate task in Specs projects),test,lint,analyse,check,ci - Utility tasks: whatever else is useful during environment setup
List all discovered tasks with their description. Prefer Task commands over raw tool invocations when an equivalent Task exists — they often handle the right flags and order automatically.
Check that task is installed:
task --version 2>/dev/null || echo "task not installed"
If a Taskfile exists but task is not installed, stop and ask the user to install it
(brew install go-task/tap/go-task on macOS) rather than running the underlying commands directly.
If there is no Taskfile, run the workflow's commands directly.
1b. Scan GitHub workflows
find .github/workflows -name "*.yml" -o -name "*.yaml" 2>/dev/null | head -20
For each workflow file found, read it and extract:
- Test jobs: unit tests, feature tests, integration tests
- Static analysis: type checkers and analysers
- Code style: formatters and style linters
- Other linters: anything else that gates the build
- Skippable jobs: jobs that use secrets, deploy steps, cloud runners (SonarCloud, Codecov uploads, etc.)
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.
- 2d ago Changed · +4 lines 3ca828f1dfca
- 7d ago First seen · 160 lines · 163 tokens per session scan A 30829c317e96
ci-green-check is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 3d ago), licensed MIT. It adds 163 tokens to every session and 1,475 once invoked, about $0.0008 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.