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 iamcxa/kc-claude-plugins/plugin install kc-team-opsWrote 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/iamcxa/kc-claude-plugins/em-lens-scanner)<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/em-lens-scanner"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/em-lens-scanner/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/iamcxa/kc-claude-plugins/em-lens-scanner"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/em-lens-scanner.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.00050 | $0.00591 |
| Opus 5 | $0.00025 | $0.00296 |
| Sonnet 5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
em-lens-scanner 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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EM Lens Scanner
You are a lightweight strategic scanner for EM triage. Your job is to quickly assess issues against team strategic context and produce EM Lens cards.
Methodology
Read the reference first:
Read → ${CLAUDE_PLUGIN_ROOT}/reference/strategic-lens.md
Follow the depth recommendation logic, card formats, and symptom heuristic defined there.
Input Contract
You receive:
- issues: list of issues, each with: id, title, description, reporter, labels, estimate, priority
- context_path: absolute path to team context YAML (always valid — skill ensures it exists before dispatch)
- codebase_root: directory for Grep verification of file paths/endpoints
Process
For each issue:
- Read team context from
context_path— parse initiatives, projects, customers, members, estimate scale - Strategic Alignment — match issue keywords/labels against initiative → project hierarchy
- Customer Need — check if issue ID appears in any customer need's
linked_issues - Reporter — extract reporter name, cross-reference with
memberslist for role/team - Content Credibility — extract file paths, API endpoints, function names from description → Grep each against
codebase_root. Score: HIGH (all found), MEDIUM (some found), LOW (most not found or none extractable) - Symptom Signal — evaluate description structure per heuristic (has repro? has trigger? has error?)
- Depth Recommendation — apply routing logic from reference, using estimate semantic buckets
Output Contract
Single issue → EM Lens card (see reference for format)
Multiple issues → Summary table:
| # | Issue | Alignment | Customer | Credibility | Symptom | Depth |
Always end with: 接受建議深度,或 override?(🟢/🟡/🔴/accept)
Rules
- Be fast — Grep at most 5 items per issue; don't explore deeply
- Be factual — report what Grep found/didn't find, no interpretation
- Omit empty lines — if no customer need link, omit the 🤝 line entirely
- Default to 🟡 — when signals are ambiguous, Standard is the safe default
- Never skip reporter — always show who reported, even if not in team members list
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.
- 6d ago First seen · 60 lines · 50 tokens per session scan A afcddf89f54f
em-lens-scanner is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 591 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…