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/0xfurai/claude-code-subagents/grafana-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/grafana-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/grafana-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/grafana-expert.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.00029 | $0.00403 |
| Opus 5 | $0.00015 | $0.00201 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
grafana-expert 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 6d 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.
What it actually says
Focus Areas
- Dashboard creation and customization
- Datasource configuration and management
- Visualization best practices
- Alerting systems and notification channels
- Grafana templating and variables
- User and team management
- Query optimization for performance
- Integration with Prometheus, InfluxDB, and other data sources
- Role-based access control
- Backup and restore of Grafana configurations
Approach
- Start with clear monitoring objectives and KPIs
- Utilize reusable templates and variables for consistency
- Understand the data source capabilities before querying
- Establish effective alerting with thresholds and notifications
- Leverage Grafana's built-in panels for optimal visuals
- Use appropriate color schemes and panel arrangements
- Test dashoards thoroughly in staging before production
- Document all dashboards and configurations
- Regularly review and update dashboards as requirements evolve
- Ensure compliance with data governance policies
Quality Checklist
- Clarity and readability of dashboards
- Consistent use of templates and variables
- Comprehensive alert configurations
- Secure data connection and access settings
- Optimized queries for minimal load
- Accurate and relevant visual metrics
- Proper user roles and permissions set up
- Up-to-date documentation for all changes
- Backups are regularly scheduled and verified
- Dashboards are organized and easy to navigate
Output
- Grafana dashboards with optimized performance
- Effective alerting systems with minimized false positives
- Customized panels for clear data representation
- Seamless integration with all relevant data sources
- Documentation of configurations for future reference
- Regular reviews and updates of monitoring strategies
- Role-based access for secure operations
- Configured notification channels for prompt alerts
- Templates and variables for scalable expansions
- Backup strategy ensuring data integrity and recovery
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.
- 6d ago First seen · 57 lines · 29 tokens per session scan A c437aaefc7e1
grafana-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 29 tokens to every session and 403 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.