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.
git clone --depth 1 https://github.com/neuromechanist/research-skillsWrote 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/rules/neuromechanist/research-skills/ci_cd)<a href="https://agentmods.dev/rules/neuromechanist/research-skills/ci_cd"><img src="https://agentmods.dev/badge/rules/neuromechanist/research-skills/ci_cd/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/rules/neuromechanist/research-skills/ci_cd"><img src="https://agentmods.dev/badge/rules/neuromechanist/research-skills/ci_cd.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.00008 | $0.00978 |
| Opus 5.5 | $0.00003 | $0.00391 |
| Sonnet 5.5 | $0.00002 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
ci_cd 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Workflow Standards
Purpose: Automated Quality Gates
Why CI/CD? Catch issues before users do. Think: Every pipeline failure is a production bug prevented. Goal: Fast feedback, high confidence, zero surprises.
Triggers and Scope (avoid wasted runs)
- Trigger:
pull_request(any base) pluspushtomain/developonly. Neveron: [push, pull_request](double runs on every PR push). - Concurrency: cancel superseded PR runs (
group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}). - Scope:
paths-ignoredocs and notes for code workflows;pathsfor docs and deploy workflows. - Required checks: a skipped workflow leaves a required check pending; use an unfiltered workflow with a gate job (see the ci-scaffolding skill).
[skip ci]: in the subject of commits that touch only files no CI job reads (see git rules).- Timeouts: every job sets
timeout-minutes(default 20); a hung job otherwise runs 6 hours. - No live services in required checks; one workflow per concern.
- Bot bump and sync commits: prefer bumping inside the PR or at release. A post-merge bot commit carries
[skip ci], alone in its push, only on the integration branch; the same workflow then deploys once from the bumped SHA (deployjobneeds: bump). If that branch later heads a release PR, the marker silences the PR's required checks; skip inside a gate job instead.
Essential Workflows
1. Testing (test.yml)
Triggers: pull_request and push to main branches, docs paths ignored
Jobs (in order):
- Lint:
ruff check/eslint(fails fast) - Test: Real tests only, matrix for versions
- Build: Verify compilation if applicable
- Coverage: Optional reporting to Codecov
2. Documentation (docs.yml)
Triggers: push to main with paths: [docs/**, mkdocs.yml]
Jobs: Build with MkDocs → Deploy to GitHub Pages
3. Release (release.yml)
Triggers: Tag creation or manual
Jobs: Build → Create release → Publish packages
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.
- 11d ago Changed · +20 lines 8429480fdf02
- 1mo ago First seen · 74 lines · 8 tokens per session scan A 4af6aa79c0db
ci_cd is a cursor rule published in the GitHub repository neuromechanist/research-skills (50 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 8 tokens to every session and 978 once invoked, about $0.0000 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-04.
Other cursor rules, from other repositories
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
fix-bugs
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
quality
Quality tooling configuration and CI pipeline for the Composer plugin.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.