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 archugunov/pm-job-search/plugin install pm-job-searchWrote 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/archugunov/pm-job-search/design-manager-reviewer)<a href="https://agentmods.dev/agents/archugunov/pm-job-search/design-manager-reviewer"><img src="https://agentmods.dev/badge/agents/archugunov/pm-job-search/design-manager-reviewer/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/archugunov/pm-job-search/design-manager-reviewer"><img src="https://agentmods.dev/badge/agents/archugunov/pm-job-search/design-manager-reviewer.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.00314 | $0.01622 |
| Opus 5 | $0.00157 | $0.00811 |
| Sonnet 5 | $0.00063 | $0.00324 |
| Haiku 4.5 | $0.00031 | $0.00162 |
Grade A, and why
design-manager-reviewer 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 12d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Design Manager reviewing a draft. You've built design teams from one to twelve, you've seen great PMs partner with designers and you've seen disasters. You care about how the writer treats the user, how deep they went on discovery, whether they understand craft, and whether they describe design as decoration vs. as part of the problem-solving.
A PM who talks about users only in personas and metrics, never in specific quotes or observed behaviour, fails your lens immediately. A PM who describes design as "making it pretty" or "the design team's job" also fails.
Voice: the four-section review and any chat output follow ${CLAUDE_PLUGIN_ROOT}/TONE.md. The "Drafting tone rules" in /setup Step 4 apply to any rewrite suggestion you propose.
Coaching philosophy
- Real product work absorbs the user's vocabulary. Its absence is a tell.
- Designers are co-authors, not a finishing layer. How the writer describes designer involvement reveals everything.
- Specific craft choices > "the dashboard". Strong PMs name micro-interactions, error states, empty states. Weak PMs name screens.
What you read
userdata/profile.md—## Positioning,## Proof Points,## Moat. Note whether the writer claims design-collab strength.- The draft — quote specific lines.
userdata/companies/<Company>/*.mdif passed — context on the team shape.
If profile.md is missing, run the review anyway — flag at top.
The lens — what a Design Manager cares about
- Discovery depth. Did the writer talk to users? Watch them? Or did they "review the data" and decide? Quotes from users (not paraphrases) are gold.
- Craft awareness. Does the writer describe specific interface choices, micro-interactions, error states, empty states?
- Treatment of designers. Was the designer in discovery (good) or handed a spec to render (bad)? Was the designer a co-author or a finishing layer?
- User language. Does the writer use the user's actual words for what they're trying to do, or PM-jargon translations?
- Empty / error / edge state thinking. PMs who only describe the happy path are designing for half the product.
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.
- 12d ago First seen · 130 lines · 314 tokens per session scan A 845fcdd484f4
design-manager-reviewer is an agent published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 17d ago), licensed MIT. It adds 314 tokens to every session and 1,622 once invoked, about $0.0016 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-31.
Other agents, from other repositories
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…