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/docs)<a href="https://agentmods.dev/rules/extsoft/elegant-git/docs"><img src="https://agentmods.dev/badge/rules/extsoft/elegant-git/docs.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.1 | $0.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
docs 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 3d 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
Docs writing
Read .cursor/references/glossary.md before naming. docs/** is
excluded from prosefmt (.config/hk.pkl); wrap prose near 100 columns yourself.
Site shape
- Numbered chapters:
NN-title.md; object parentsNN-00-<object>.md; actionsNN-MM-<object>-<action>.md. - Front matter:
layout: default;titleequals H1;nav_order; prettypermalink. Children setparent:to the parent title exactly. Parents addhas_children: trueandhas_toc: false. - Titles:
"self" guide(not"eg self" guide); anatomyCLI anatomy; action pageseg self configure. - Cross-link with relative
.mdpaths.
Object landing (xx-00)
Short lead, then ## Actions first — unordered list, one-line purposes from commandGroups in
internal/cli/commands.go. Then concept. No per-action ## plus fenced bash.
# BAD
title: self
## configure
```bash
eg self configure
See eg self configure.
GOOD
title: '"self" guide'
Actions
configure— Configures Git and the Elegant Git installation.
## Action pages
Lead with what the command is for. One short `bash` invocation, explanation after it. `##`
headings are topics (`What it applies`), never `Synopsis` / `Arguments` / `See also`.
Second-person prose; bullets only for real lists; tables stay in `docs/reference/`.
Write from the Go implementation. Skip hidden/deprecated commands.
## Vocabulary
- **Elegant Git installation** — this machine’s `eg` (shared memory, acquired, aliases).
- **Git configuration** — `git config` (identity, standards). Do not say “Git installation” for
`self`.
- `git elegant` is a feature (git alias after configure), not leftover. Do not lead with the
`git-elegant` binary or completions unless the page is about upgrading.
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.
- 3d ago First seen · 57 lines · 0 tokens per session scan A e5a1c33ea57e
docs is a cursor rule published in the GitHub repository extsoft/elegant-git (47 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 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-09-03.
Other cursor rules, from other repositories
bypass_websearch
Bypass built-in WebSearch.
conservative-file-creation
Check for existing files before creating. Be conservative about new files and code.
repository-layout
Canonical map of repo folders and docs.
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.