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/extsoft/elegant-gitWrote 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/extsoft/elegant-git/glossary)<a href="https://agentmods.dev/rules/extsoft/elegant-git/glossary"><img src="https://agentmods.dev/badge/rules/extsoft/elegant-git/glossary/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/extsoft/elegant-git/glossary"><img src="https://agentmods.dev/badge/rules/extsoft/elegant-git/glossary.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.00024 | $0.00132 |
| Opus 5.5 | $0.00010 | $0.00053 |
| Sonnet 5.5 | $0.00005 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
glossary 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.
What it actually says
Glossary
Canonical terms live in .cursor/references/glossary.md. Read it before inventing names.
When updating the glossary:
- One canonical term per concept; keep entries short (
### Termblocks, no tables). - Preserve existing entries unless the user approves changes; never silently rename.
- Merge duplicates; call out conflicts before overwriting.
- Format: definition sentence; optional
Aliases:,Avoid:,Notes:.
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 · 16 lines · 24 tokens per session scan A fe49ae7790aa
glossary is a cursor rule published in the GitHub repository extsoft/elegant-git (48 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 132 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
development-workflow
Version control, code quality, and development environment standards.
workflow
Git branching strategy, commit conventions, and pull request workflow.
beads
This project uses Beads (bd) for issue tracking.
github-workflow
GitHub invariants — standard flow on listed use cases; no issue spam; tick linked checklists before merge.
commits
Commit message standards and conventions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.