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 agents/andrewaltimit/template-repo/github-etiquettegit clone --depth 1 https://github.com/AndrewAltimit/template-repoWhat 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.00000 | $0.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
github-etiquette 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Etiquette for AI Agents
This document provides essential guidelines for AI agents interacting with GitHub issues, pull requests, and comments.
Critical Rules
1. @ Mentions - Use with Extreme Caution
NEVER use @ mentions for:
- AI agent names (Gemini, Claude, OpenAI, etc.)
- Generic role names (reviewer, developer, tester)
- Any name you're not 100% certain is a real contributor
ONLY use @ mentions for:
- Repository owner: @AndrewAltimit
- Contributors explicitly listed in the repository
- Users who have specifically requested to be mentioned
Why this matters: Using @Gemini or @Claude will ping random GitHub users who happen to have those usernames, causing unnecessary notifications and confusion.
2. Referencing AI Agents
Correct ways to reference AI agents:
- "Gemini's review indicates..."
- "As Claude suggested..."
- "The OpenAI agent found..."
- "Per the agent's analysis..."
Incorrect ways (DO NOT USE):
- "@Gemini's review indicates..." [WRONG]
- "As @Claude suggested..." [WRONG]
- "CC @OpenAI for visibility..." [WRONG]
3. Comment Formatting
When posting automated comments:
- Clearly identify yourself as an AI agent
- Use professional, concise language
- Include relevant context without being verbose
- End with a signature line indicating automated generation
Example:
## Automated Code Review
I've analyzed the changes and found the following...
[Review content]
---
*This review was automatically generated by [Agent Name] AI.*
4. Issue and PR Interactions
When creating issues:
- Use clear, descriptive titles
- Label appropriately
- Include all necessary context
- Never assign to users without permission
When commenting on PRs:
- Focus on constructive feedback
- Acknowledge good practices, not just issues
- Provide actionable suggestions
- Respect the author's time and effort
5. Error Handling
If you make a mistake (like incorrect @ mention):
- Acknowledge it promptly in a follow-up comment
- Update documentation to prevent recurrence
- Learn from the feedback
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 · 123 lines · 0 tokens per session scan A ec4a599b807a
github-etiquette is an agent published in the GitHub repository AndrewAltimit/template-repo (131 stars, last pushed 1mo ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 760 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-08-30.
Other agents, from other repositories
agent-system
An AgentSystem composes multiple Agents into a directed graph that Orloj executes as a coordinated workflow. The graph defines how messages flow between agents during task execution.
Deep Research
Execute a recursive, hypothesis-driven deep dive research workflow — orchestrating corpus scanning, web scouting, source fetching, sprint synthesis, bibliography enrichment, and academic paper generation. Instantiates the workflow defined in docs/guides/deep-research.md.
Executive PM
Maintain the health of the repository as an open-source resource — issues, labels, milestones, changelog, contributing docs, and community standards.
Executive Researcher
Orchestrate research sessions end-to-end — delegate to the research fleet, synthesize outputs, and spawn new area-specific research agents as needed.
Research Synthesizer
Transform raw Scout findings into structured, opinionated synthesis documents in docs/research/ following the expansion→contraction pattern.
Executive Docs
Maintain and evolve all project documentation — encoding dogmatic values, guiding axioms, and methodology across every documentation layer.