Little-Claude: Command for Claude Code

.claude/commands/trellis/check-backend.md

check-backend is a command for Claude Code from qingyu321/Little-Claude. It costs 0 tokens per session (157 once invoked), scanned A, a copy of check-backend, Apache-2.0.

A command that reviews recently changed backend code against the project's backend development guidelines.

In plain words
What is it for?
It checks the Git changes, selects the relevant backend guidance, and reports or fixes problems it finds.
Why use it?
It helps catch violations of rules for databases, errors, logging, types, and general code quality after implementation.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is qingyu321/Little-Claude's own configuration. It tells Claude Code how to work on Little-Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Little-Claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to qingyu321/Little-Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/commands/trellis/check-backend.md
Clone the repo
git clone --depth 1 https://github.com/qingyu321/Little-Claude

Made for: Claude Code.

Wrote 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.

agentmods badge for check-backend

README.md
[![agentmods](https://agentmods.dev/badge/commands/qingyu321/little-claude/check-backend/github.svg)](https://agentmods.dev/commands/qingyu321/little-claude/check-backend)
Your own site
<a href="https://agentmods.dev/commands/qingyu321/little-claude/check-backend"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/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.

agentmods 80×15 button for check-backend

Your own site · 80×15
<a href="https://agentmods.dev/commands/qingyu321/little-claude/check-backend"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/check-backend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 157 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 4e81a28d681e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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 9d 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.

Origin

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.

.claude/commands/trellis/check-backend.md · 14 lines

What it actually says

Check if the code you just wrote follows the backend development guidelines.

Execute these steps:

  1. Run git status to see modified files
  2. Read .trellis/spec/backend/index.md to understand which guidelines apply
  3. 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
  4. Review your code against the guidelines
  5. Report any violations and fix them if found
Changes

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.

  1. 9d ago First seen · 14 lines · 0 tokens per session scan A 4e81a28d681e

Subscribe to this mod's changes

check-backend is a command published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 15d 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.