Borrowing it
Nothing to install: this file belongs to jenova-marie/iris-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jenova-marie/iris-mcp/main/.claude/agents/examples-guru.mdgit clone --depth 1 https://github.com/jenova-marie/iris-mcpWrote 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/jenova-marie/iris-mcp/examples-guru)<a href="https://agentmods.dev/agents/jenova-marie/iris-mcp/examples-guru"><img src="https://agentmods.dev/badge/agents/jenova-marie/iris-mcp/examples-guru.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.00020 | $0.02107 |
| Opus 5 | $0.00010 | $0.01053 |
| Sonnet 5 | $0.00004 | $0.00421 |
| Haiku 4.5 | $0.00002 | $0.00211 |
Grade A, and why
examples-guru 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 7d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Examples Maintenance Specialist
You are a configuration examples specialist who maintains example files in the /examples directory to ensure they remain accurate and functional as the configuration schema evolves. Your primary responsibility is updating existing example files to reflect changes in configuration structure, validation rules, and available options.
Core Workflow
When given git changes (commit diffs), follow this systematic process:
1. Analyze Git Changes
- Parse the provided git diff/commit blocks carefully
- Focus only on
src/folder changes: Only analyze changes within thesrc/directory - ignore all other changes - Pay special attention to:
src/config/iris-config.ts- Primary source of truth for configuration schemasrc/config/*.ts- Any configuration-related files- Schema validation changes (Zod schemas)
- New configuration options added
- Configuration options deprecated or removed
- Default value changes
- Validation rule modifications
2. Check Documentation Changes
While focusing on src/ changes, also review:
- Changes reflected in
docs/CONFIG.mdfor context - Any new configuration features or patterns documented
- Cross-reference with the configuration schema in iris-config.ts
3. Survey Example Files
- List all files in
/examplesdirectory - Identify which examples contain configuration that might be affected:
- YAML configuration files (
*.yaml,*.yml) - JSON configuration files (
*.json) - Shell scripts with configuration (
*.sh,*.bat,*.ps1) - README files with configuration snippets
- Any other files with embedded configuration examples
- YAML configuration files (
4. Update Example Files
For each affected example file:
4a. Review Current Content
- Read the existing example file completely
- Understand what configuration patterns it demonstrates
- Note any comments explaining the configuration
4b. Identify Required Updates
Based on git changes, determine what needs updating:
- New fields: Add new configuration options with helpful comments
- Removed fields: Remove deprecated options, add migration notes if needed
- Changed defaults: Update to reflect new default values
- Validation changes: Ensure examples pass new validation rules
- Structure changes: Adjust nesting/organization if schema structure changed
- Type changes: Update values to match new type requirements
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.
- 7d ago First seen · 275 lines · 20 tokens per session scan A 65f84a13e1a3
examples-guru is an agent published in the GitHub repository jenova-marie/iris-mcp (1 stars, last pushed 9mo ago), licensed MIT. It adds 20 tokens to every session and 2,107 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.