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 VilnaCRM-Org/php-service-template --skill ci-workflowgit clone --depth 1 https://github.com/VilnaCRM-Org/php-service-templateWrote 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/vilnacrm-org/php-service-template/ci-workflow)<a href="https://agentmods.dev/skills/vilnacrm-org/php-service-template/ci-workflow"><img src="https://agentmods.dev/badge/skills/vilnacrm-org/php-service-template/ci-workflow/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/vilnacrm-org/php-service-template/ci-workflow"><img src="https://agentmods.dev/badge/skills/vilnacrm-org/php-service-template/ci-workflow.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.00020 | $0.00381 |
| Opus 5.5 | $0.00008 | $0.00152 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
ci-workflow 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 2mo 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
CI Workflow
Goal
Validate the repository using the commands that currently back GitHub Actions for this template.
Full Verification Stack
Run the relevant subset for the change. For application code, default to the full stack:
make composer-validate
make check-requirements
make check-security
make phpcsfixer
make psalm
make psalm-security
make phpinsights
make deptrac
make setup-test-db
make unit-tests
make integration-tests
make behat
make infection
make generate-openapi-spec
make generate-graphql-spec
Rules
- Prefer
maketargets. - If a command needs the PHP container, do not bypass Docker wrappers.
- Do not lower thresholds in
phpinsights.php. - Do not loosen Deptrac rules in
deptrac.yaml. - Do not weaken coverage or mutation settings just to make the job pass.
Common Failure Routing
make phpcsfixeror style drift: fix formatting, then rerun the stack.make psalmormake psalm-security: fix types or taint issues in code.make phpinsights: usecomplexity-management.make deptrac: usedeptrac-fixer.make unit-tests/make integration-tests/make behat/make infection: usetesting-workflow.- Spec drift after API change: use
openapi-development.
Minimum Close-Out
Before marking a code change complete, confirm:
- relevant checks pass locally, or
- you explicitly state what could not be run and why, and
- the remaining validation is delegated to GitHub Actions.
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.
- 2mo ago First seen · 58 lines · 20 tokens per session scan A 4c5f1ae3082a
ci-workflow is a skill published in the GitHub repository VilnaCRM-Org/php-service-template (25 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 20 tokens to every session and 381 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-30.
Other skills, from other repositories
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
testing-and-ci
Choose and run unit, E2E, Caddyfile fixture, automation, and CI checks for caddy-security. Use for coverage requirements, test evidence, failures, and report workflows; official OP conformance remains opt-in.