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/rashadansari/myagents/agents-mdgit clone --depth 1 https://github.com/RashadAnsari/myagentsWrote 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/rashadansari/myagents/agents-md)<a href="https://agentmods.dev/instructions/rashadansari/myagents/agents-md"><img src="https://agentmods.dev/badge/instructions/rashadansari/myagents/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.00839 | $0.00839 |
| Opus 5 | $0.00419 | $0.00419 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
myagents 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Rules & Conventions
Rules for all agents and subagents working in this repository.
Review Crew Sync Rule
When a new review agent is added to plugins/albino/agents/, the following MUST be updated in the same change:
plugins/albino/commands/reviewcrew.md: add the new agent to the "Spawn All Reviewers in Parallel" list (Step 1) and add its corresponding section to the report structure (Step 3).
plugins/albino/commands/pr-review.md: add the new agent to the predefined reviewer list in Step 6 ("Select Relevant Reviewers"), including the detection rule that determines when it should be included based on changed file types or paths. If the agent is always relevant regardless of file type, add it to the "Always include" list.
Failure to update both files when adding a review agent is a violation of this rule.
Review agents are any agent file whose name ends in -reviewer.md inside plugins/albino/agents/.
Skill Reminder Rule
The mandatory skill list is injected once at session start via two mechanisms that must always stay in sync:
plugins/albino/hooks/session-start.sh: runs on Claude Code (SessionStarthook) and Cursor (sessionStarthook). The Cursor branch is currently a no-op due to a platform bug whereadditional_contextis silently dropped. Keep the hook in place for when Cursor fixes it.plugins/albino/rules/session-start.mdc: active workaround for Cursor. Injected as analwaysApplyrule viaplugins/albino/.cursor-plugin/plugin.json. This is the mechanism that actually delivers context to Cursor agents today.
The skills currently injected:
dev-conventionsresearch-firstagent-memory
These skills are mandatory and always active. Additional skills are available in plugins/albino/skills/ but are opt-in and not injected automatically.
When a new skill is added to plugins/albino/skills/, ask the user:
"A new skill
<name>was added. Do you want it included in the agent reminder so it is enforced on every task?"
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 · 77 lines · 839 tokens per session scan A b2d2c82f88da
myagents AGENTS.md is an instructions file published in the GitHub repository RashadAnsari/myagents (6 stars, last pushed 29d ago), licensed MIT. It adds 839 tokens to every session, about $0.0042 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
codedb AGENTS.md
AGENTS.md instructions for justrach/codedb, covering codedb agent guidelines, what codedb is (and isn't), review guidelines, pre-merge verification and security-sensitive areas.
Puppetmaster AGENTS.md
AGENTS.md instructions for professorpalmer/Puppetmaster, covering agents.md, first: are you a puppetmaster worker?, default subagent runtime: puppetmaster, when to start a puppetmaster swarm (do this by default) and match the verb to the task shape (single feature ≠ swarm).
agent-skills AGENTS.md
Instructions for powabase-ai/agent-skills, covering agents.md, repository structure, prerequisites & commands, writing skill.md files and frontmatter (required).
cosmos-mcp CLAUDE.md
Instructions for teampolarity/cosmos-mcp, covering cosmos-mcp, layout, tools (authoritative list in src/tools/index.ts), cli subcommands and imessage is the headline source.
mcp-httpserver-proxy AGENTS.md
Instructions for shailesh17/mcp-httpserver-proxy, covering agent guidelines for mcp-httpserver-proxy, 🎯 repository overview, ⚠️ critical constraints & rules, 1. standard output (stdout) is sacred and 2. transport lifecycle order.
vibe-mcp AGENTS.md
Instructions for VibeTechnologies/vibe-mcp, covering vibe-mcp agent memory, canonical eval reference, relay and connection semantics, what counts as real e2e and fake extension test harness rules.