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/tecnomanu/agent-rules-kitWrote 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/tecnomanu/agent-rules-kit/05-template-processing)<a href="https://agentmods.dev/rules/tecnomanu/agent-rules-kit/05-template-processing"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/05-template-processing/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/tecnomanu/agent-rules-kit/05-template-processing"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/05-template-processing.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.00849 |
| Opus 5.5 | $0.00000 | $0.00340 |
| Sonnet 5.5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
05-template-processing 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Processing & Variables
This document explains how templates are processed and variables are substituted in Agent Rules Kit.
Template Variables
The following variables are available for use in template files:
| Variable | Description | Example |
|---|---|---|
{projectPath} |
Path to the project | /path/to/project |
{detectedVersion} |
Detected version of the framework | 10 |
{versionRange} |
Compatible version range | v10-11 |
{stack} |
Selected stack | laravel |
Processing Flow
- Read Template: Templates are read from
templates/directory - Process Variables: All variables in
{placeholder}format are replaced - Add Front Matter: Metadata is added as front matter to MDC files
- Output Generation: Processed content is written to destination
Implementation
The main processing happens in cli/utils/file-helpers.js:
// Process template variables (simplified example)
const processTemplateVariables = (content, meta = {}) => {
let processedContent = content;
// Replace all template variables with their values
const templateVariables = [
{ value: meta.detectedVersion, replace: 'detectedVersion' },
{ value: meta.versionRange, replace: 'versionRange' },
{ value: meta.projectPath, replace: 'projectPath' },
{ value: meta.stack, replace: 'stack' }
];
templateVariables.forEach(({ value, replace }) => {
if (value) {
const regex = new RegExp(`\\{${replace}\\}`, 'g');
processedContent = processedContent.replace(regex, value);
}
});
return processedContent;
};
Example
Template file:
# {stack} Documentation
This project is using {stack} version {detectedVersion}.
It is located at {projectPath}.
After processing (if stack=laravel, detectedVersion=10, projectPath=/app):
# laravel Documentation
This project is using laravel version 10.
It is located at /app.
Template Structure Guidelines
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 · 125 lines · 0 tokens per session scan A 0013860e5845
05-template-processing is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit (36 stars, last pushed 1y ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 849 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.