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.
npx agentmods add rules/sordi-ai/skill-everything/domain-templategit clone --depth 1 https://github.com/sordi-ai/skill-everythingWrote 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/sordi-ai/skill-everything/domain-template)<a href="https://agentmods.dev/rules/sordi-ai/skill-everything/domain-template"><img src="https://agentmods.dev/badge/rules/sordi-ai/skill-everything/domain-template.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00870 |
| Opus 5 | $0.00012 | $0.00435 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
domain-template 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 4d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Skill: Domain Knowledge Template
Purpose: Structured template for capturing company- or project-specific knowledge that no public model can know — architecture decisions, naming conventions, business rules.
Instructions: Fill Out This Template
Copy this file to skills/<project-name>/SKILL.md and fill in all sections.
Delete empty sections. Concrete > comprehensive.
Project Overview
Project name: [e.g. "OrderFlow"]
Technology: [e.g. "Node.js 20, PostgreSQL 15, React 18"]
Deployment: [e.g. "AWS ECS, GitHub Actions CI/CD"]
Team size: [e.g. "4 backend, 2 frontend"]
Main repo: [e.g. "github.com/acme/orderflow"]
Architecture Decision Records (ADRs)
ADR-001: [Title]
- Date: YYYY-MM-DD
- Status: Accepted / Deprecated / Superseded by ADR-XXX
- Context: Why did a decision need to be made?
- Decision: What was decided?
- Consequences: What changes as a result?
Naming Conventions
| Context | Convention | Example |
|---|---|---|
| Database tables | snake_case, plural | order_items |
| API endpoints | kebab-case, plural | /api/order-items |
| TypeScript interfaces | PascalCase, no I prefix |
OrderItem |
| Environment variables | SCREAMING_SNAKE_CASE | DATABASE_URL |
| React components | PascalCase | OrderItemList |
Business Rules
These rules are not documented in the code — only here.
- [Rule name]: [Description]. Example:
Orders under $10 have no shipping costs. - [Rule name]: [Description].
Known Pitfalls
- [Pitfall]: [What happens and why]. Example:
The users table has two ID fields: id (internal) and external_id (customer number). Never confuse them. - [Pitfall]: [What happens and why].
External Systems & Integrations
| System | Purpose | Auth Method | Contact for Issues |
|---|---|---|---|
| Stripe | Payments | API key in STRIPE_SECRET_KEY |
[email protected] |
| SendGrid | Emails | API key in SENDGRID_API_KEY |
[email protected] |
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.
- 4d ago First seen · 113 lines · 24 tokens per session scan A 1de441b8808b
domain-template is a cursor rule published in the GitHub repository sordi-ai/skill-everything (20 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 870 once invoked, about $0.0001 per session on Opus 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-30.
Other cursor rules, from other repositories
00-stack
Stack, runtimes, and MCP servers for this repository.
20-testing
How to run tests and MCP smoke checks.
30-security
Secrets, gitleaks, age encryption, telemetry redaction.
obsidian-memory
Markdown vault memory protocol (vkm-kit).
10-style
Style conventions and contribution hygiene.
schema
Scalable and secure schema design patterns for relational databases, NoSQL, and APIs. / TR: İlişkisel veri tabanları, NoSQL ve API'ler için ölçeklenebilir ve güvenli şema tasarım kalıpları.