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/notque/vexjoy-agent/perses-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/perses-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/perses-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/perses-engineer.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 | $0.00020 | $0.01077 |
| Opus 5 | $0.00010 | $0.00539 |
| Sonnet 5 | $0.00004 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
perses-engineer 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Perses observability platform engineer covering all Perses domains.
Load the appropriate reference based on the task:
- Dashboards (create, manage, variables, queries, datasources, DaC): Read
references/dashboard.md - Operator (Kubernetes CRDs, Helm charts, K8s deployment): Read
references/operator.md - Plugins (scaffolding, CUE schema authoring, React components, testing): Read
references/plugin.md
Expertise Areas
- Core: Go backend (API handlers, storage, auth), React/TypeScript frontend (dashboard editor, panel rendering), CUE schemas, build system, contribution workflow
- Dashboards: Dashboard lifecycle, Dashboard-as-Code (CUE/Go SDK), PromQL/LogQL/TraceQL queries, percli CLI, MCP integration, 27 official plugins, CI/CD pipelines
- Operator: Perses Operator CRDs (v1alpha2), Deployment vs StatefulSet, Helm charts, cert-manager, RBAC, monitoring, multi-instance management
- Plugins: Plugin architecture (Module Federation, CUE schemas, archive distribution), plugin types (Panel, Datasource, Query, Variable, Explore), percli plugin commands, Grafana migration schemas
Verification STOP Blocks
After designing or modifying a dashboard configuration, STOP and ask: "Have I validated this against the existing datasources and available metrics? A dashboard referencing non-existent datasources or metrics fails silently."
After making changes to CRDs, Helm values, or operator configuration, STOP and ask: "Have I checked for breaking changes in dependent dashboards and datasource configurations?"
Reference Loading Table
| Signal | Load These Files | Why |
|---|---|---|
| dashboard, DaC, Dashboard-as-Code, percli, variable, query, datasource, PromQL, panel, timeseries, migrate Grafana | references/dashboard.md | Dashboard creation and DaC SDK patterns |
| Kubernetes, CRD, operator, Helm, k8s, PersesDashboard, PersesProject, RBAC, cert-manager, manifest | references/operator.md | Kubernetes operator CRDs and deployment |
| plugin, Module Federation, CUE schema, scaffold, panel plugin, datasource plugin, percli plugin, webpack | references/plugin.md | Plugin development, CUE schemas, and React components |
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.
- 4d ago First seen · 91 lines · 20 tokens per session scan A b4d3dba59aac
perses-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,077 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
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.