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 event4u-app/agent-config --skill github-cigit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/github-ci)<a href="https://agentmods.dev/skills/event4u-app/agent-config/github-ci"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/github-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/event4u-app/agent-config/github-ci"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/github-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.00043 | $0.01158 |
| Opus 5 | $0.00022 | $0.00579 |
| Sonnet 5 | $0.00009 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
github-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 9d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
github-ci
When to use
Use this skill when working with GitHub Actions workflows, CI pipeline configuration, or understanding the automated quality and deployment process.
Procedure: Modify CI workflows
- Read
.github/workflows/to understand the full pipeline. - Check
AGENTS.mdfor quality tool commands and testing setup. - Read
commands/fix/ci.mdfor CI failure debugging workflow.
Workflow overview
Quality pipeline (quality-tests.yml)
Triggered on: pull_request to main, workflow_dispatch
Read .github/workflows/ to discover the actual job matrix. Common patterns:
- PHP version is extracted from Dockerfile (
ARG PHP_VERSION), not hardcoded. - Static analysis may run on larger runners for memory.
- Tests run in parallel with a matrix strategy per test suite.
- Branch comparison for dead code and API docs.
Deployment workflows
| Workflow | Trigger | Environment |
|---|---|---|
deploy-review.yaml |
PR with review-env label |
Review (ephemeral) |
deploy-sta.yaml |
Push to main |
Stage |
deploy-pro.yaml |
Tag release-X.Y.Z or schedule (Mon 8AM) |
Production |
deploy.yml |
After "Static Code Analysis" succeeds on main |
Envoyer trigger |
module-deploy.yaml |
Reusable workflow (called by others) | Parameterized |
Other workflows
| Workflow | Purpose |
|---|---|
pr-review-gate.yaml |
Points-based review system (see code-review skill) |
destroy-review.yaml |
Cleanup ephemeral review environments |
add-labels.yml |
Auto-label PRs |
apply-pr-template.yaml |
Apply PR description template |
validate-deployment-files.yaml |
Validate AWS deployment configs |
template-db-dump.yaml |
Database dump utility |
Conventions
Workflow structure
- Use pinned action versions with SHA hashes (not tags):
actions/checkout@<sha> # v6.0.2 - Use concurrency groups to prevent duplicate runs:
group: ${{ github.workflow }}-${{ github.ref }} - Use
fail-fast: falsein matrix strategies for independent job execution. - Extract shared logic into reusable workflows (
module-deploy.yamlpattern). - A job with
container:MUST rungit config --global --add safe.directory "$GITHUB_WORKSPACE"immediately afteractions/checkout— the checkout is owned by a different UID than the container user, so without it every git-backed step dies withfatal: detected dubious ownership.
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.
- 9d ago First seen · 129 lines · 43 tokens per session scan A fa0ef77ebd95
github-ci is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,158 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-09-03.
Other skills, from other repositories
CI Pipeline Optimizer
Optimize CI test pipelines through intelligent test splitting, parallelization, caching strategies, and selective test execution based on code changes.
Flaky Test Quarantine
Detect, quarantine, and systematically fix flaky tests with automated retry analysis, root cause categorization, and CI pipeline integration for test reliability.
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.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.
Advanced Chaos Engineering
Advanced chaos engineering patterns using Chaos Monkey, Litmus, and Gremlin for testing distributed system resilience under failure conditions.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.