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 instructions/parzival1l/altru/agents-mdgit clone --depth 1 https://github.com/parzival1l/AltruWrote 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/instructions/parzival1l/altru/agents-md)<a href="https://agentmods.dev/instructions/parzival1l/altru/agents-md"><img src="https://agentmods.dev/badge/instructions/parzival1l/altru/agents-md.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.01069 | $0.01069 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
Altru AGENTS.md 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 5d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions (Workspace)
Root instruction file for Cursor/Claude agents in this monorepo. Deeper AGENTS.md files override this one for their subtree.
What this repo is
Altru is a Quebec-focused charity discovery + donation tax-optimizer demo. Three runtimes share one tree:
| Folder | Runtime | Default port | Purpose |
|---|---|---|---|
frontend/ |
Vite 5 + React 18 + TS | 5173 | UI; proxies /api → backend |
backend/ |
Node + Express + TS (tsx watch) |
3002 | JSON API; bridges frontend → agent via adk CLI |
agent/ |
Botpress ADK (@botpress/runtime) |
3000 bot / 3001 console | RAG over CRA charity corpus; owns searchCharities workflow |
data/ |
Source data + generated artifacts | — | CRA TSV input + curated seed JSON + ingest outputs |
scripts/ |
Dev orchestration + ingest pipeline | — | launch-dev.sh, ingest-charities.ts, RAG smoke |
End-to-end request shape: Frontend → POST /api/search → Express → adk workflows run searchCharities → Botpress KB → OpenAI rationale → hydrated Charity records back to UI.
Always-applied rules
[.cursor/rules/core.mdc](.cursor/rules/core.mdc)— TDD (Red→Green→Refactor), architecture-SSOT update rule, confirm before edits >3 files / API / auth / data shape.[.cursor/rules/git.mdc](.cursor/rules/git.mdc)— branch before commit (cursor/<topic>), appenddocs/ACTIVITY.md, never commit/push without explicit confirmation.[.cursor/rules/botpress-adk.mdc](.cursor/rules/botpress-adk.mdc)— applies insideagent/and to anything generating ADK code.
Single sources of truth (do not duplicate, do update)
[docs/architecture.md](docs/architecture.md)— system design, API contracts, Mermaid diagram. Update in the same commit as any service / API / data-flow change.[docs/ACTIVITY.md](docs/ACTIVITY.md)— session-level changelog. Append after every substantive change.[docs/feature-process.md](docs/feature-process.md)— phase-level feature tracker. Update only when a phase status changes.[docs/local-testing.md](docs/local-testing.md)— canonical "how to run everything" (ports, scripts, flags).
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.
- 5d ago First seen · 57 lines · 1,069 tokens per session scan A f14cbf186519
Altru AGENTS.md is an instructions file published in the GitHub repository parzival1l/Altru (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,069 tokens to every session, about $0.0053 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).