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/parzival1l/altru/gitgit clone --depth 1 https://github.com/parzival1l/AltruWhat 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.00018 | $0.00590 |
| Opus 5 | $0.00009 | $0.00295 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
git 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Altru — Git and Activity Logging
When to use this rule: Whenever you finish a task, touch versioned project files, or the user asks about history or commits.
Branch-First (Pull Requests)
For changes intended for GitHub as a PR:
git fetch originand check outmain,git pullto start current.git checkout -b cursor/<short-description>— informative name, prefixcursor/for agent-driven work.- Make edits, then stage / commit only after explicit user confirmation.
- After commit,
git push -u origin <branch>only after explicit user confirmation, then open a PR (compare →main).
Exception: Direct commits on main only when the user explicitly requests it (e.g. hotfix). Still requires confirmation before git commit / git push.
Commit and Push Rules
- Never run
git add/git commitwithout explicit user confirmation each time. - Never run
git pushwithout explicit user confirmation each time. No auto-push. - Multiple prompts without committing is normal — do not assume the user wants to commit.
- After completing substantive work, ask whether to commit (offer a suggested message). If declined, continue; ask again after the next batch of changes.
- Commit and push are always separate offers unless the user explicitly says both in one message.
Typical Flow
- Finish task → update
docs/ACTIVITY.md. - Ask whether to stage and commit now (suggest a message). Wait for confirmation.
- If they commit and want remote updated → ask again separately before
git push.
docs/ACTIVITY.md Entries
Append a timestamped entry to docs/ACTIVITY.md after every substantive set of changes.
Entry Format
## YYYY-MM-DD HH:MM ET — [brief title]
- **Files:** `path/one`, `path/two`
- **What:** …
- **Why:** …
- **Commands:** … (or "none")
Time: Always include clock time in US Eastern Time with suffix ET.
Get current time: TZ=America/New_York date '+%Y-%m-%d %H:%M'
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.
- yesterday First seen · 60 lines · 18 tokens per session scan A 8d400bbc0902
git is a cursor rule published in the GitHub repository parzival1l/Altru (2 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 590 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-31.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.