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/setupnpx skills add panaversity/agentfactory-business-plugins --skill setupgit 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/setup)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/setup"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/setup.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.00058 | $0.00957 |
| Opus 5 | $0.00029 | $0.00478 |
| Sonnet 5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
setup 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTIC OFFICE SETUP
This skill creates your work.local.md workplace memory file from the
bundled template and orients you to the two-plugin architecture.
STEP 1 — LOAD CONTEXT
Read work.local.md in the current working directory.
If it already exists, skip to STEP 4 (orientation only).
STEP 2 — CREATE WORK.LOCAL.MD
Copy the template from ${CLAUDE_PLUGIN_ROOT}/work.local.md.template
to work.local.md in the current working directory.
Tell the user:
I have created work.local.md from the Agentic Office template.
This file is your four-layer workplace memory — the foundation
for all professional intelligence features.
STEP 3 — GUIDED CONFIGURATION
Walk the user through filling in each layer interactively:
Layer 1 — Personal: Ask for: name, role, working style, decision-making approach, current focus (top 1-3 priorities), working hours, communication preference.
Layer 2 — Team (People): Ask: "Who are the 5-8 people you interact with most? For each, I need: name, role, how they prefer to receive information, and what they are working on right now."
Layer 3 — Projects: Ask: "What are your active projects? For each: name, any internal codename, current status, priority (P1/P2/P3), and what is happening right now."
Layer 4 — Organisational: Ask: "What internal terms, acronyms, or codenames would confuse an outsider? What are your recurring meetings? Any unwritten rules that every colleague knows but nobody writes down?"
After each layer, write the entries to work.local.md and confirm.
STEP 4 — ORIENTATION MESSAGE
Deliver this orientation:
Your Agentic Office uses two plugins working together:
OFFICIAL PRODUCTIVITY PLUGIN (Anthropic)
/productivity:start — Initialise TASKS.md + CLAUDE.md + dashboard
/productivity:update — Sync from external tools, triage stale items
Provides: Basic task CRUD, two-tier memory, visual dashboard
AGENTIC OFFICE PLUGIN (Panaversity)
9 professional intelligence skills:
workplace-context — Four-layer workplace memory (work.local.md)
workplace-search — Cross-context search across all memory layers
task-intelligence — Brain dump capture, P1/P2/P3 prioritisation
delegation — Delegation quality standard + handoff comms
digest — Daily morning briefing assembly
meeting-intelligence — Three-phase meeting model (before/during/after)
progress-tracker — RAG status, milestones, blocker classification
context-loader — Cross-domain context injection
executive-brief — Situation briefs (pre-meeting, decision, person)
4 persistent agents:
chief-of-staff — Orchestration: digest delivery, threshold alerts
memory-keeper — work.local.md maintenance, trigger-based updates
meeting-intelligence-agent — Calendar-triggered prep and post-meeting synthesis
work-tracker — Delegation lifecycle, overdue protocol
The official plugin handles task and memory CRUD.
The agentic office adds professional intelligence on top.
Try: "Give me my daily digest" or "Brain dump my priorities"
What ships with it
2 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 · 117 lines · 58 tokens per session scan A cc70137965e5
setup is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (28 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 957 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 skills, from other repositories
remember
Recall what was actually said or decided earlier — across daily summaries, the conversation buffer, files people sent, live sessions and scheduled runs. Use whenever someone refers to prior context ("what did we decide", "last time", "as I said", "the file I sent you", "what did you tell me"), or for any synonym of…
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.
brain-sync
Sync knowledge and learnings to the shared appie-brain repo. Every Appie commits with their own identity so contributions are traceable. Use after: complex tasks (5+ tool calls), significant discoveries, new skills, or client work. Fleet: Appie-1 (Orchestrator/MacMini), Appie-2 (CMO/DO), Appie-3 (CTO/VPS).
project-context-sync
Keep a living project state document updated after each commit, so any agent (or future session) can instantly understand where things stand.
memory-search
Search and retrieve information from the Appie brain — daily logs, project notes, decisions, topics, and long-term memory files stored in /.hermes/memory/. Use this skill whenever you need to recall past conversations, decisions, project context, personal preferences, or anything discussed previously.