Borrowing it
Nothing to install: this file belongs to qxchuckle/qcqx-project-manage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qxchuckle/qcqx-project-manage/master/.cursor/commands/trellis-check-backend.mdgit clone --depth 1 https://github.com/qxchuckle/qcqx-project-manageWrote 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/commands/qxchuckle/qcqx-project-manage/trellis-check-backend)<a href="https://agentmods.dev/commands/qxchuckle/qcqx-project-manage/trellis-check-backend"><img src="https://agentmods.dev/badge/commands/qxchuckle/qcqx-project-manage/trellis-check-backend/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/commands/qxchuckle/qcqx-project-manage/trellis-check-backend"><img src="https://agentmods.dev/badge/commands/qxchuckle/qcqx-project-manage/trellis-check-backend.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.00000 | $0.00157 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
trellis-check-backend 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.
This is a copy
100% identical to check-backend — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check if the code you just wrote follows the backend development guidelines.
Execute these steps:
- Run
git statusto see modified files - Read
.trellis/spec/backend/index.mdto understand which guidelines apply - Based on what you changed, read the relevant guideline files:
- Database changes →
.trellis/spec/backend/database-guidelines.md - Error handling →
.trellis/spec/backend/error-handling.md - Logging changes →
.trellis/spec/backend/logging-guidelines.md - Type changes →
.trellis/spec/backend/type-safety.md - Any changes →
.trellis/spec/backend/quality-guidelines.md
- Database changes →
- Review your code against the guidelines
- Report any violations and fix them if found
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 First seen · 14 lines · 0 tokens per session scan A 4e81a28d681e
trellis-check-backend is a command published in the GitHub repository qxchuckle/qcqx-project-manage (4 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 157 tokens. A static security scan graded it A with 0 findings. It is 100% identical to check-backend, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
evaluate-connector
Evaluate a Fivetran connector for correctness, SDK compliance, security, and reliability.
connector-review
Review DataHub connector code for standards compliance and quality.
review-rust
Focused Rust/Tauri backend review with rust-backend-architect (Primary Owner).
api-style-review
Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
document
On-demand documentation generation — API docs, architecture updates, user guides.