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/pjt222/agent-almanacWrote 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/agents/pjt222/agent-almanac/_template)<a href="https://agentmods.dev/agents/pjt222/agent-almanac/_template"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/_template/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/pjt222/agent-almanac/_template"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/_template.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00723 |
| Opus 5.5 | $0.00007 | $0.00289 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
your-agent-name 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Agent Name
A comprehensive description of what this agent does and its primary use cases.
Purpose
Explain the specific problem this agent solves or the workflow it enhances.
Capabilities
- Primary Capability: What the agent does best
- Secondary Capabilities: Additional features and functionalities
- Tool Integration: How it leverages available tools
- MCP Integration: Any MCP server integrations (if applicable)
Available Skills
List the skills from the skills library this agent can execute. Use bare skill IDs (the slash-command names). Group by domain if the agent spans multiple domains, or use a flat list for a small number of skills.
Usage Scenarios
Scenario 1: Primary Use Case
Brief description of the main scenario where this agent excels.
Example command or interaction pattern
Scenario 2: Alternative Use Case
Description of another common use case.
Example command or interaction pattern
Best Practices
- Guideline 1: How to get the best results
- Guideline 2: Common pitfalls to avoid
- Guideline 3: When to use this agent vs others
Examples
Example 1: Basic Usage
User: [Example user request]
Agent: [Expected agent response/behavior]
Example 2: Advanced Usage
User: [Complex user request]
Agent: [Expected agent response/behavior]
Configuration Options (Optional)
Document any configurable parameters, environment variables, or settings that affect this agent's behavior.
| Option | Default | Description |
|---|---|---|
option_name |
default_value |
What this option controls |
Tool Requirements (Optional)
If this agent requires specific tools beyond the standard set, document them here. Include any MCP server dependencies, external CLIs, or API keys needed.
Limitations
- Known limitation 1
- Known limitation 2
- Situations where this agent might not be appropriate
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.
- 1mo ago First seen · 109 lines · 17 tokens per session scan A e027d8a2e39d
your-agent-name is an agent published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 723 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
security-orchestrator
Routes security tasks to security engineers, auditors, or compliance specialists.
recruiter
Sources, screens, and hires top talent. Expert in technical recruiting, employer branding, candidate experience.
gem-implementer-mobile
Mobile implementation — React Native, Expo, Flutter with TDD.
implementation-plan
Generate an implementation plan for new features or refactoring existing code.
tdd-refactor
Improve code quality, apply security best practices, and enhance design whilst maintaining green tests and GitHub issue compliance.