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 jeremylongworth-source/AgentSkills --skill ci-workflow-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/ci-workflow-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/ci-workflow-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/ci-workflow-plan/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/jeremylongworth-source/agentskills/ci-workflow-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/ci-workflow-plan.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.00061 | $0.00335 |
| Opus 5.5 | $0.00024 | $0.00134 |
| Sonnet 5.5 | $0.00012 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
ci-workflow-plan 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
CI Workflow Plan
Core Workflow
- Identify repository type, languages, build artifacts, test layers, release needs, and target CI host.
- Define triggers, jobs, dependencies, caching, artifacts, environment variables, secrets, and permissions.
- Add quality gates: lint, typecheck, unit, integration, E2E, security, package, and publish checks as appropriate.
- Keep secrets scoped and write permissions minimal.
- Define failure reporting, retry policy, required checks, and branch protection expectations.
- Include migration notes when moving between CI hosts.
Safety Rules
- Do not add broad write tokens, unreviewed secrets, or deploy-on-every-branch workflows without explicit approval.
- Do not claim CI commands pass without output.
- Verify host-specific syntax from current docs when implementing a real workflow file.
Deliverable Shape
For CI workflow plans, provide:
- CI host and repository assumptions
- Trigger and job plan
- Quality gates
- Cache and artifact plan
- Secrets and permission model
- Required checks
- Failure and retry behavior
- Validation steps
References
- Read
references/ci-workflow-plan-checklist.mdwhen planning or reviewing CI workflows.
What ships with it
2 files 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.
- 1mo ago First seen · 47 lines · 61 tokens per session scan A 2da34f1577ca
ci-workflow-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 61 tokens to every session and 335 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.
e2e-automation-project
Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first.
deploy-templates
Built-in deploy recipes and deploy targets. Use when a task asks you to set up or change a stage/preprod/prod deploy workflow, including the system's "Set up deploy" tasks.
matlab-testing-ci
MATLAB testing, validation, and CI workflow for matlab.unittest, MATLAB Test, Simulink Test, coverage, artifact generation, GitHub Actions, and open-source reproducibility. Use whenever MATLAB work needs verification, regression tests, CI, GitHub publication, or acceptance criteria.
wicked-garden-platform-security-engineer
Security scanning and vulnerability assessment from DevSecOps perspective. Use when: security review, vulnerability assessment, OWASP Top 10 scan, secrets detection, dependency audit, CI/CD pipeline security review, or as the triage rubric behind the platform domain's security action. NOT THIS WHEN: a scenario-driven…