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/craigcossairt/trellisWrote 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/craigcossairt/trellis/project)<a href="https://agentmods.dev/rules/craigcossairt/trellis/project"><img src="https://agentmods.dev/badge/rules/craigcossairt/trellis/project/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/craigcossairt/trellis/project"><img src="https://agentmods.dev/badge/rules/craigcossairt/trellis/project.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.00317 | $0.00317 |
| Opus 5.5 | $0.00127 | $0.00127 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
project 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
Read AGENTS.md at the repo root and follow it - it is the canonical instruction file for all
AI agents on this project. Full methodology docs live in docs/methodology/ (TDD workflow,
bug-fix protocol, session habits). Append bug patterns to docs/common-gotchas.md and decisions
to docs/decision-log.md as described in AGENTS.md § Autonomous Housekeeping.
Guardrail hooks for Cursor are wired in .cursor/hooks.json (same scripts Claude Code runs;
trust the workspace so they load). Honor the rules they enforce even if hooks aren't firing:
never edit secrets or lock files, and run bash bin/verify-green.sh before pushing when the
push gate is configured.
Skills in .cursor/skills/ are routers, not procedures. Each is frontmatter plus one sentence
naming a canonical file under .claude/ - read that file when a router matches the task, and
never fork its body into the router. Copy the canonical description verbatim: in Cursor it is
the trigger, so a reworded one silently stops matching phrases the canonical skill answers to.
While this directory exists, adding a skill or command under .claude/ means adding its router
in the same commit; hooks CI fails either half of that pair going missing. If the project drops
Cursor support, delete .cursor/ outright and the rule no longer applies.
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 · 24 lines · 317 tokens per session scan A 6c063e294911
project is a cursor rule published in the GitHub repository craigcossairt/trellis (5 stars, last pushed 8d ago), licensed MIT. It adds 317 tokens to every session, about $0.0013 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
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
no-auto-commit
Never commit or push without explicit user instruction.
methodology
Learn-by-building methodology — how the AI must behave in this repo.
checks
How to add or modify a scanner check.