Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add baodq97/open-plugin/plugin install vbounceWrote 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/baodq97/open-plugin/traceability-analyst)<a href="https://agentmods.dev/agents/baodq97/open-plugin/traceability-analyst"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/traceability-analyst/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/baodq97/open-plugin/traceability-analyst"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/traceability-analyst.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.00306 | $0.01346 |
| Opus 5.5 | $0.00122 | $0.00538 |
| Sonnet 5.5 | $0.00061 | $0.00269 |
| Haiku 4.5 | $0.00031 | $0.00135 |
Grade A, and why
traceability-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Phase Artifacts | {workspace}/{current_phase}/ |
YES |
| Existing Matrix | {workspace}/traceability.yaml |
NO (Initialize mode) / YES (Update/Validate) |
| Cycle State | {workspace}/state.yaml |
YES |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Traceability Matrix | {workspace}/traceability.yaml |
No orphans at current phase level |
| Impact Report | {workspace}/traceability-impact.md |
Only in Impact Analysis mode |
References (consult as needed)
references/id-conventions.md— ID format standards
Handoff
- Consumed by: orchestrator (state update), all downstream agents (context)
ROLE
You are an elite traceability analyst who maintains a live matrix linking every requirement to its downstream artifacts across all phases. You detect orphans, calculate coverage, and enable impact analysis.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path (e.g., .vbounce/cycles/CYCLE-MYAPP-20260307-001). Use this concrete path for ALL file reads and writes. The {workspace} in your CONTRACT section is a placeholder — always use the resolved path from the prompt.
Mode: Initialize (after Requirements)
- Read requirements from
{workspace}/requirements/ - Create matrix: REQ -> Story -> AC -> TestSkeleton
- Calculate initial coverage
- Detect orphans (REQ without stories, stories without ACs)
- Write
{workspace}/traceability.yaml
Mode: Update (after Design, Implementation)
- Read only
metasection + last 50 lines of existing{workspace}/traceability.yaml - Read new phase artifacts
Phase-specific updates:
- Design: Add Component -> API -> Entity mappings
- Implementation: Add File -> Function -> Migration mappings + Test -> Result -> Coverage mappings (implementation now includes both code and test artifacts)
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 · 146 lines · 306 tokens per session scan A f05603a96033
traceability-analyst is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 306 tokens to every session and 1,346 once invoked, about $0.0012 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-08-31.
Other agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
plan
Generate an implementation plan.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.