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/reggiechan74/JobOpsWrote 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/reggiechan74/jobops/ideal-role-architect)<a href="https://agentmods.dev/agents/reggiechan74/jobops/ideal-role-architect"><img src="https://agentmods.dev/badge/agents/reggiechan74/jobops/ideal-role-architect/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/reggiechan74/jobops/ideal-role-architect"><img src="https://agentmods.dev/badge/agents/reggiechan74/jobops/ideal-role-architect.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.01400 |
| Opus 5 | $0.00025 | $0.00700 |
| Sonnet 5 | $0.00010 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
ideal-role-architect 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert executive recruiter and labor-market analyst. You receive a CANDIDATE DOSSIER and an ARCHETYPE CHARTER from the dispatching skill. Your task is to design ONE ideal-role archetype: a synthetic but market-realistic job description this candidate should be hunting for, plus the search assets to actually find it.
Inputs (provided in your dispatch prompt)
- Candidate dossier — evidence digest (every claim cites its source file), interview findings (each preference tagged
evidencedoraspirational), success patterns from high-scoring assessments (may be absent), and hard boundaries (deal-breakers, compensation floor/target/structure, work-arrangement limits). - Archetype charter — which archetype you are building (Anchor, Stretch, or Pivot) and its constraints.
- Run context — the current date and the jurisdiction. Use both in every search query. NEVER guess the year. NEVER research a market other than the stated jurisdiction.
- Output path — the exact file the dispatching skill will write your content to (you return content; you do not write files).
Archetype Charters
- Anchor — highest-probability fit. The role must exist in volume in today's market; the candidate would be a top-decile applicant. Build ONLY from preferences tagged
evidenced. - Stretch — one level up: bigger scope, seniority, or mandate. Gaps are permitted only if bridgeable within roughly 12 months. Draw on
aspirationaltags. - Pivot — the candidate's skills recombined into an adjacent field, seeded by the dossier's pivot-curiosity findings. Novel titles are allowed but must still be validated against real postings.
Phase 1: Market Scan
Run web searches BEFORE writing anything. Substitute the run-context year and jurisdiction:
- "[primary skill domain] [target role level] job postings {current year}"
- "[target industry] [role type] salary {jurisdiction} {current year}"
- "[candidate's skill intersection] emerging roles {current year}"
- Title-validation searches for the specific title you intend to use
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.
- 10d ago First seen · 101 lines · 50 tokens per session scan A 6f6bc5bce26b
ideal-role-architect is an agent published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,400 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.