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 panaversity/agentfactory-business-plugins --skill matchgit clone --depth 1 https://github.com/panaversity/agentfactory-business-pluginsWrote 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/panaversity/agentfactory-business-plugins/match)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/match"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/match.svg" alt="Measured on agentmods" 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.00109 | $0.01927 |
| Opus 5 | $0.00055 | $0.00963 |
| Sonnet 5 | $0.00022 | $0.00385 |
| Haiku 4.5 | $0.00011 | $0.00193 |
Grade A, and why
match 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 8d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UNIVERSAL RULES (apply to every talent matching task)
- NEVER base a readiness assessment on tenure alone -- years in role does not equal readiness for next role
- NEVER omit the motivation / career intent dimension -- developing someone toward a role they do not want is wasteful and can backfire if the development leads to them leaving
- NEVER classify a gap as "NOT A FIT" without evidence -- distinguish between "not ready" and "not suited"
- NEVER produce a talent assessment without the CONFIDENTIAL label
- NEVER share a talent assessment with the employee being assessed without explicit HR and manager review and decision
- NEVER make a specific promotion commitment in a talent assessment output -- these assessments inform decisions; they are not decisions
- ALWAYS include specific recommended actions for each candidate
BEFORE IMPLEMENTATION
| Source | Check |
|---|---|
| Conversation | Role requirements (critical, important, nice-to-have), candidate names and current roles, assessment context (vacancy, succession, or development mapping) |
| hr.local.md | Performance review cycle dates, promotion cycle timing, internal mobility policy, competency framework in use |
| Prior outputs | /jd output for the target role requirements (if a JD has been written for this role) |
CLARIFICATION QUESTIONS
Required (ask if not provided):
- What role or level are candidates being assessed for?
- Who are the candidates? (at least 2 names with current roles and tenure)
- Is this a current vacancy, succession planning, or development mapping?
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 228 lines · 109 tokens per session scan A cf47c997f4b8
match is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 109 tokens to every session and 1,927 once invoked, about $0.0005 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 skills, from other repositories
internal-linking-optimizer
An analysis tool for the links within a website. Internal links are links from one page of a site to another page on the same site.
geo-review-html
Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in…
memory-read
Query-first indexing and retrieval for Operator OS memory. Use when asked to find prior context, search memory, rebuild the memory index, or answer from the workspace without loading large files by default.
memory-manage
Manage Active updates, atomic session handoffs, and human-gated Long-Term proposals. Use when asked to remember something, preserve a decision, log meaningful work, or review memory.
security-risk-scan
Use when reviewing a code change for auth, input validation, secrets, permissions, or unsafe side effects.
lead-matcher
Use when the user wants to identify which Macao people, companies, or institutions are worth researching or approaching.