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.
npx skills add laboramus-ai/laboramus-ai-claude-plugin --skill analyze-rolegit clone --depth 1 https://github.com/laboramus-ai/laboramus-ai-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/skills/laboramus-ai/laboramus-ai-claude-plugin/analyze-role)<a href="https://agentmods.dev/skills/laboramus-ai/laboramus-ai-claude-plugin/analyze-role"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/analyze-role/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/skills/laboramus-ai/laboramus-ai-claude-plugin/analyze-role"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/analyze-role.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.00053 | $0.00515 |
| Opus 5 | $0.00026 | $0.00258 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
analyze-role 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Laboramus — Analyze Role
Extract what the role requires, independent of any candidate. This needs only the job posting — no CV. It lets a user understand a job before uploading anything. Output: analyses/role-requirements.md.
(Separate from compare-fit, which compares these requirements against the candidate's profile.)
Input
job-posting.md (pasted text or scraped).
What to extract → role-requirements.md
Readable Markdown in the user's language:
Role summary
Title + 2–3 sentences on what the role is about.
Required hard skills
Each: skill · Must-Have vs. Nice-to-Have (based on posting wording: "required/essential" = Must-Have; "desirable/a plus" = Nice-to-Have) · any specified level/years.
Required soft skills (explicit + role-typical)
- Explicit: soft skills the posting names directly.
- Role-typical (advantage profile): the soft skills that typically give an advantage in this kind of role, derived from the role itself — even if the posting doesn't spell them out. E.g. a software architect: communication/translation between business and engineering, influence without authority, ambiguity tolerance, long-term/systems thinking, consensus-building. Mark these clearly as "typically advantageous for this role" (a probabilistic guide, not a hard requirement). Keep it grounded and role-specific — not generic platitudes.
Key responsibilities
The main duties, prioritized (Critical / High / Medium) by prominence in the posting.
Seniority level of the target role
State the level the role sits at (IC / Lead / Head / C-level). This matters for later fit/career-logic.
Sparse-posting inference
If the posting is short, infer standard requirements from the job title (e.g. "Business Analyst" → SQL, requirements engineering, stakeholder management) and mark them as inferred, not quoted.
Next step
If no candidate profile exists yet, tell the user: "This is what the role requires. Upload your CV / build your profile, and I'll compare it against these requirements (the personal fit comparison)."
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 · 38 lines · 53 tokens per session scan A 5d20b5a3c2f2
analyze-role is a skill published in the GitHub repository laboramus-ai/laboramus-ai-claude-plugin (2 stars, last pushed 13d ago), licensed MIT. It adds 53 tokens to every session and 515 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…