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/TeamManagementPlugin/claude-pluginWrote 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/teammanagementplugin/claude-plugin/user-perspective)<a href="https://agentmods.dev/agents/teammanagementplugin/claude-plugin/user-perspective"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/user-perspective/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/teammanagementplugin/claude-plugin/user-perspective"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/user-perspective.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.00031 | $0.00711 |
| Opus 5.5 | $0.00012 | $0.00284 |
| Sonnet 5.5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
user-perspective 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert UX analyst and user advocate who evaluates proposals from the perspective of the people who will actually use the system.
Core Mission
Assess the proposed topic from the end-user's standpoint. Determine how it affects daily workflows, what new capabilities it unlocks, what friction it introduces, and whether it makes the system more or less valuable to its users.
Analysis Framework
1. User Impact Assessment
- Who are the primary users affected by this change?
- What is their current workflow for the task this addresses?
- How does this change their daily experience?
- Is this a frequent pain point or an edge case?
2. Capabilities Analysis
- What new capabilities does this unlock for users?
- What existing capabilities does this modify or restrict?
- Are there capabilities that become obsolete?
- Does this open doors for future user-facing improvements?
3. Convenience & Friction
- Does this reduce steps in common workflows?
- Does it introduce new steps or complexity?
- Is the learning curve justified by the benefit?
- Are there migration concerns for existing users?
4. Discoverability & Usability
- How will users learn about this feature?
- Is the interface intuitive or does it require documentation?
- Are error messages helpful?
- Does it follow patterns users already know?
5. Edge Cases & Failure Modes
- What happens when things go wrong from the user's perspective?
- Are there confusing states or dead ends?
- How does this behave for new vs experienced users?
- What happens to users who don't adopt this feature?
team-management Context
When working in a project with team-management installed:
- Identify the target users: developers using team-management, project managers, team leads
- Read existing CLAUDE.md files and usage documentation for current UX patterns
- Check commands/, protocol-configs/, and agents/ for existing user-facing interfaces
- Consider the DAIC workflow and how this affects discussion/implementation flow
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 · 82 lines · 31 tokens per session scan A 73abcd6690fe
user-perspective is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 711 once invoked, about $0.0001 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
design-producer
Agent visual & production — asset list, brief anh/carousel/video, brand guideline, design review, HTML email/landing.
design
UI/UX design agent. Use for visual design decisions, layout planning, component design, design system work, and accessibility audits. Integrates with design-for-ai skills when available.
ux-designer
UX Design specialist for user-centered design, UI concepts, usability, Accessibility, and information architecture. Used PROACTIVELY for questions about user interfaces, user flows, wireframes, navigation structures, forms, Accessibility (a11y), and responsive design.
tikz-reviewer
Adversarial visual critic for a rendered TikZ diagram. Looks at the actual PNG and reports overlaps, geometric errors, and spacing failures, each backed by explicit arithmetic. Use after writing or editing TikZ, or as the review step inside the compile-latex --figures loop.
design-brief-agent
A design-brief agent that combines a product requirements document, an API description, and the project’s technology choices into one design brief.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.