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/Stramp/Lost-Mines-PhandelverWrote 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/stramp/lost-mines-phandelver/ci-cd)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/ci-cd"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/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/stramp/lost-mines-phandelver/ci-cd"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/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.00893 | $0.00893 |
| Opus 5.5 | $0.00357 | $0.00357 |
| Sonnet 5.5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Rules (Continuous Integration/Continuous Deployment)
Concept
CI/CD automates build, test and deploy processes, ensuring code always compiles and works correctly.
Recommended Pipeline
1. Build (Compilation)
ALWAYS compile the project on each commit/pull request.
Objective: Detect compilation errors immediately.
2. Tests
ALWAYS run tests automatically after successful build.
Objective: Detect regressions and bugs.
3. Code Validation
ALWAYS validate:
- Formatting (clang-format)
- Linting (clang-tidy, if configured)
- Static analysis (if configured)
Objective: Maintain code quality and consistency.
4. Documentation Validation
ALWAYS verify:
- README.md exists and is updated
- ARCHITECTURE.md is updated (if there are architectural changes)
- Comments in new code
Objective: Ensure documentation is always updated.
GitHub Actions Configuration
Example: .github/workflows/build.yml
name: Build and Test
on:
push:
branches: [ master, main, develop ]
pull_request:
branches: [ master, main, develop ]
jobs:
build:
runs-on: windows-latest
steps:
- uses: actions/checkout@v3
- name: Setup Unreal Engine
# Configure Unreal Engine path
- name: Generate Project Files
run: |
"C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\RunUBT.bat" -projectfiles -project="${{ github.workspace }}\MyProject2.uproject" -game -engine
- name: Build Project
run: |
"C:\Program Files\Epic Games\UE_5.7\Engine\Build\BatchFiles\Build.bat" MyProject2Editor Win64 Development "${{ github.workspace }}\MyProject2.uproject" -waitmutex
- name: Run Tests
run: |
# Run automated tests
# (when implemented)
- name: Validate Code Format
run: |
# Check formatting with clang-format
# (when configured)
CI/CD Rules
1. Build Must Always Pass
- NEVER commit code that doesn't compile
- If build fails, fix before continuing
- Use CI to validate before merge
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 · 161 lines · 893 tokens per session scan A 4d6c9fca49b7
ci-cd is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 893 tokens to every session, about $0.0036 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-31.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
cursor-asdd
ASDD contribution rules for this repository.
agents
Agent engineering standards — Agents (TR-SEC-003).
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
infrastructure
Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning.