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 agentmods add skills/panaversity/agentfactory-business-plugins/referencenpx skills add panaversity/agentfactory-business-plugins --skill referencegit 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/reference)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/reference"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/reference.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 | $0.00094 | $0.01937 |
| Opus 5 | $0.00047 | $0.00968 |
| Sonnet 5 | $0.00019 | $0.00387 |
| Haiku 4.5 | $0.00009 | $0.00194 |
Grade A, and why
reference 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 4d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UNIVERSAL RULES (apply to every reference task)
- NEVER provide a reference that is inconsistent with the employee's documented performance record -- this creates legal and ethical risk
- NEVER include salary information without the employee's explicit consent
- NEVER provide a reference that you personally do not believe to be true -- if you cannot provide a positive reference, provide factual only
- NEVER send a reference without HR review, especially for former employees who left on difficult terms
- NEVER include information about disciplinary matters, health conditions, or protected characteristics in any reference
- ALWAYS include the "REVIEW BEFORE SENDING" warning in every output
BEFORE IMPLEMENTATION
| Source | Check |
|---|---|
| Conversation | Employee name, reference type requested (factual/professional/verification), recipient and purpose if known |
| hr.local.md | Reference policy (factual only vs professional permitted), company letterhead information, HR signatory details, rehire eligibility policy |
| Prior outputs | None — /reference is typically invoked independently |
CLARIFICATION QUESTIONS
Required (ask if not provided):
- Who is the reference for? (employee name)
- What type of reference is needed? (factual / professional / employment verification)
Optional (ask if context suggests value):
- Who is the recipient and what is the purpose? (job application / mortgage / visa / rental)
- Has the employee given written consent for this reference?
- Is there specific information the recipient has requested?
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.
- 4d ago First seen · 252 lines · 94 tokens per session scan A b0612384b63e
reference is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (28 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,937 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
Use when improving internal link structure, anchor text, orphan pages, crawl depth, site architecture, or link equity flow. 内链优化/站内架构.
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…
schedule
Create, list, remove or inspect this bot's scheduled work — recurring jobs ("every morning at 7 tell me X", "every weekday at 9 post the standup") and one-shot follow-ups ("check back in 20 minutes", "watch that deploy until it lands", "remind me on Friday"). Use whenever something must happen on a schedule…
kanban-codex-lane
Use when a Hermes Kanban worker wants to run Codex CLI as an isolated implementation lane while Hermes keeps ownership of task lifecycle, reconciliation, testing, and handoff.
coding-agents
Delegate coding tasks to external autonomous AI coding CLI agents — Claude Code, Codex, OpenCode, and Kanban+Codex lane patterns. Covers install, auth, one-shot tasks, interactive sessions, PR reviews, parallel worktrees, and reconciliation.
code-quality
Code quality and verification: codebase metrics, post-implementation cleanup, and pre-commit verification pipeline.