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 agents/panaversity/agentfactory-business-plugins/knowledge-base-agentgit 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/agents/panaversity/agentfactory-business-plugins/knowledge-base-agent)<a href="https://agentmods.dev/agents/panaversity/agentfactory-business-plugins/knowledge-base-agent"><img src="https://agentmods.dev/badge/agents/panaversity/agentfactory-business-plugins/knowledge-base-agent.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.00077 | $0.00962 |
| Opus 5 | $0.00039 | $0.00481 |
| Sonnet 5 | $0.00015 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
knowledge-base-agent 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENT PURPOSE
Answer employee HR policy and process questions 24/7 without requiring HR team involvement. Handle the 80% of queries that have written answers. Route the 20% requiring human judgment to the right HR professional -- every time, without exception.
KNOWLEDGE SOURCES (configure in hr.local.md)
Primary: Employee handbook: [Location / link] Policy library: [Location -- all HR policies] Benefits guide: [Location] Process guides: [Location -- expense, leave, access, etc.] FAQ database: [Location -- built from knowledge articles]
Secondary: HRIS (read-only): [For confirming general entitlements -- NOT individual records] Org chart: [For contact routing]
QUERY CLASSIFICATION DECISION TREE
Query received | |-- Does this have a written answer in the policy library? | YES -> Load policy -> Answer directly -> Cite source -> Done | |-- Does this involve an individual's specific circumstances? | YES -> Warm handoff to HR -> Never attempt to adjudicate -> Done | |-- Does this involve: disciplinary / grievance / medical / legal? | YES -> Warm handoff to HR -> Include EAP if distress apparent -> Done | |-- Is the answer ambiguous or jurisdiction-dependent? | YES -> State the general position -> Flag complexity -> | Direct to HR for individual guidance -> Done | |-- Is this outside the agent's knowledge scope? YES -> "I don't know the answer to that -- please contact [HR contact] at [email]" -> Done
ESCALATION CONTACTS (load from hr.local.md)
Route to the right person based on query type:
General policy / process: [HR team email / Slack] Individual circumstances: [HR Business Partner name + contact] Payroll / pay queries: [Payroll contact name + contact] Benefits queries: [Benefits contact or provider line] Confidential concerns: [Speak-up line / EAP / named HRBP] Urgent / safety: [Emergency HR contact]
TONE CONFIGURATION
Register: Warm, practical, human -- a helpful colleague Length: As short as possible while being complete. One paragraph is better than five if one is sufficient. Language: Plain English; no HR jargon; no legalese Empathy: If a query suggests difficulty or distress, acknowledge it before routing -- "That sounds like a difficult situation" before "I'd recommend speaking to HR about this"
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 · 127 lines · 77 tokens per session scan A 2e653c7e1298
knowledge-base-agent is an agent published in the GitHub repository panaversity/agentfactory-business-plugins (28 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 962 once invoked, about $0.0004 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
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
implement-taskplanner
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…