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/SYZ-Coder/codebase-knowledge-wikiWrote 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/syz-coder/codebase-knowledge-wiki/backend-service-spec-skill)<a href="https://agentmods.dev/rules/syz-coder/codebase-knowledge-wiki/backend-service-spec-skill"><img src="https://agentmods.dev/badge/rules/syz-coder/codebase-knowledge-wiki/backend-service-spec-skill/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/syz-coder/codebase-knowledge-wiki/backend-service-spec-skill"><img src="https://agentmods.dev/badge/rules/syz-coder/codebase-knowledge-wiki/backend-service-spec-skill.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.01282 |
| Opus 5.5 | $0.00000 | $0.00513 |
| Sonnet 5.5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
backend-service-spec-skill 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Service Spec Skill
Use this rule when the user asks to understand, map, document, or maintain reusable knowledge for backend systems, legacy systems, microservices, platform services, service chains, APIs, MQ flows, scheduled jobs, or central knowledge base pages.
Do not use this rule for ordinary feature implementation, bug fixes, test writing, or refactors unless the user explicitly asks for code knowledge mapping as part of the work.
Required Skill Source
Before producing artifacts, read the skill source from one of these locations:
- If this skill library exists in the target project:
backend-service-spec-skill/SKILL.md - If copied under a shared skill folder:
skills/backend-service-spec-skill/SKILL.md - If cloned as a project-local rule source:
ai-skill-lib/backend-service-spec-skill/SKILL.md - If only this rule is available, follow the summarized workflow below and state that the full skill source was not found.
Also read only the directly relevant reference files when they exist:
backend-service-spec-skill/references/workspace-classification.mdbackend-service-spec-skill/references/codemap-modes.mdbackend-service-spec-skill/references/router-map.mdbackend-service-spec-skill/references/domain-layering.mdbackend-service-spec-skill/references/service-deep-dive.mdbackend-service-spec-skill/references/central-repo-conventions.mdbackend-service-spec-skill/references/quality-checklist.mdbackend-service-spec-skill/references/output-templates.mdbackend-service-spec-skill/references/diagram-output-guidelines.mdbackend-service-spec-skill/references/mermaid-safety-checklist.zh-CN.md
Command Intents
Treat these text commands as workflow intents, not as built-in executable commands:
create_codemapservice_deep_divecrate_router_mapcreate_router_mapbuild_domain_map
If the target project provides scripts or CLI commands for these intents, prefer running them from the integrated terminal. Common locations to check:
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 · 158 lines · 0 tokens per session scan A f3fc940a39c6
backend-service-spec-skill is a cursor rule published in the GitHub repository SYZ-Coder/codebase-knowledge-wiki (9 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,282 tokens. 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
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.