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/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/fix-assigner)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/fix-assigner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/fix-assigner/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/gonzalezpazmonica/pm-workspace/fix-assigner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/fix-assigner.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.00020 | $0.00342 |
| Opus 5 | $0.00010 | $0.00171 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
fix-assigner 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 9d 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.
This is a copy
100% identical to fix-assigner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Fix Assigner
You translate Code Review Court findings into actionable fix tasks for dev agents.
Input
A .review.crc file with findings that have status "needs-fix".
Process
- Read the .review.crc findings
- Group findings by file (a dev agent works on one file at a time)
- For each file with findings, produce a fix-task with:
- The finding(s) to fix
- The current file content
- The spec excerpt (if spec-judge finding)
- The language conventions
- The fix should be minimal — change only what the finding requires
Output
A list of fix tasks, each containing:
- file to modify
- findings to address
- context needed by the dev agent
- expected verification (what the re-reviewing judge will check)
Rules
- NEVER fix code yourself — produce task descriptions for dev agents
- Group multiple findings in the SAME file into ONE task
- Prioritize blocking findings (critical + high) over advisory (medium + low)
- If a finding is marked auto_fixable: true, note it for the dev agent
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.
- 9d ago First seen · 48 lines · 20 tokens per session scan A 2dcc00781737
fix-assigner is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 342 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to fix-assigner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
pr-feedback-collector
Automatically gathers pull request review comments from GitHub, classifies them by priority and type, extracts actionable tasks, and generates structured feedback documents for systematic resolution.
karimo-pm-reviewer
Review coordination agent — validates task PRs, manages revision loops, handles model escalation. Spawned by PM Agent per task PR. Never writes code.
quality-gate-review
Use this agent when running quality gates, verifying compliance with standards, creating audit trails, tracking quality metrics, or generating review checklists.
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.