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/ongridio/ongrid/specialist-computegit clone --depth 1 https://github.com/ongridio/ongridWrote 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/ongridio/ongrid/specialist-compute)<a href="https://agentmods.dev/agents/ongridio/ongrid/specialist-compute"><img src="https://agentmods.dev/badge/agents/ongridio/ongrid/specialist-compute.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.00036 | $0.01181 |
| Opus 5 | $0.00018 | $0.00590 |
| Sonnet 5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
specialist-compute 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 75 lines · 36 tokens per session scan A 7ca75ba3f632
specialist-compute is an agent published in the GitHub repository ongridio/ongrid (988 stars, last pushed yesterday), licensed AGPL-3.0. It adds 36 tokens to every session and 1,181 once invoked, about $0.0002 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
prometheus-expert
Designs Prometheus scraping, alerting rules, and dashboards aligned with operational SLOs.
grafana-expert
Builds Grafana dashboards and alerting pipelines, aligning metrics with SLOs and operational reporting.
error-tracking
Manage Datadog Error Tracking including issue search, triage, assignment, and lifecycle management.
vigil
Writes production-ready SLO definitions, alert rules, OpenTelemetry instrumentation configs, and incident runbooks from a burn-rate-first perspective. Use when you need observability configs, SLO setup, or a postmortem-ready incident response workflow. Trigger with "set up my SLOs", "write my alert runbook".
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
playwright-test-healer
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…