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/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/success-metrics-defined)<a href="https://agentmods.dev/agents/infraspecdev/tesseract/success-metrics-defined"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/success-metrics-defined/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/infraspecdev/tesseract/success-metrics-defined"><img src="https://agentmods.dev/badge/agents/infraspecdev/tesseract/success-metrics-defined.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.00059 | $0.00446 |
| Opus 5.5 | $0.00024 | $0.00178 |
| Sonnet 5.5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
success-metrics-defined 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.
What it actually says
Success Metrics Defined (PM8)
Description
Grade ONE PM dimension: does the doc state HOW we will know the work succeeded after it ships? This is a plan-level / research-level check — distinct from the PRD-Review dim 3 structural check on a PRD's metrics section. Return a single-check JSON block — no prose.
Inputs
doc_path— absolute path to the plan, research findings, RFC, or proposal under review
Check
| ID | Eval point | Severity | Pass criterion |
|---|---|---|---|
| PM8 | Success metrics | Important | The doc defines at least one measurable outcome (numeric threshold, target percentage, time-bound goal, observable behavioral change) that determines "this worked". Vague "improve X" / "users will be happier" / "support tickets should drop" without a measurement fails. |
Grade A (fully met) / B (minor gap) / C (partial) / D (barely) / F (absent).
Output shape (JSON only)
{
"id": "PM8",
"name": "Success metrics",
"persona": "product-manager",
"grade": "A|B|C|D|F",
"severity": "Important",
"evidence_quote": "<verbatim line from the doc, or empty string if absent>",
"gap": "<one sentence, or null if grade A>",
"suggestion": "<one sentence, or null if grade A>"
}
evidence_quote MUST be a verbatim substring of the doc; do not paraphrase.
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 · 46 lines · 59 tokens per session scan A 252e1737da2a
success-metrics-defined is an agent published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 446 once invoked, about $0.0002 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-09-03.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.