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 workplace-contextgit 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/workplace-context)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/workplace-context"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/workplace-context.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.00080 | $0.01275 |
| Opus 5 | $0.00040 | $0.00638 |
| Sonnet 5 | $0.00016 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
workplace-context 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WORKPLACE MEMORY WORKFLOW
STEP 1 — LOAD CONTEXT
Read work.local.md in the current working directory.
If it does not exist, tell the user to run /agentic-office:setup first.
STEP 2 — IDENTIFY REQUEST TYPE
TYPE 1: ADD PERSON Input: Name, role, reporting line, communication style, current focus, any sensitivities Output: Formatted person entry for work.local.md Layer 2 + confirmation
PERSON ENTRY FORMAT:
- name: "[Full name]"
role: "[Job title]"
reports_to: "[Manager name]"
communication: >
[How they prefer to receive information; what works; what annoys them]
current_focus: "[What they are working on right now]"
priorities: "[Their current top 1-3 priorities]"
note: "[Anything important about working with this person]"
sensitivity: "[Optional — anything that must not be shared broadly]"
TYPE 2: ADD PROJECT Input: Project name, codename, status, priority, owner, description, current milestone, risks, decisions already made Output: Formatted project entry for work.local.md Layer 3 + confirmation
PROJECT ENTRY FORMAT:
- name: "[Project full name]"
codename: "[Internal codename if different]"
status: "[PLANNING / IN PROGRESS / AT RISK / BLOCKED / COMPLETE]"
priority: "[P1 / P2 / P3]"
owner: "[Named person]"
description: >
[What this project is; why it matters; key context]
current_milestone: "[What is happening now]"
next_milestone: "[What comes next; by when]"
at_risk: "[What could go wrong; what is currently stalled]"
decisions: ["[Decision made; date]"]
key_contacts: ["[Person; role in project]"]
TYPE 3: ADD TERM Input: Term, definition, when to use, when NOT to use, related terms Output: Formatted terminology entry in Layer 4 + confirmation
TERMINOLOGY ENTRY FORMAT:
"[Term]": >
[Definition in plain language — what it means in this organisation]
Use: [When this term is appropriate]
Not: [When NOT to use it — external comms? formal docs? pre-announcement?]
Related: [Synonyms or near-synonyms]
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.
- 8d ago First seen · 167 lines · 80 tokens per session scan A 3f80267ef6a9
workplace-context is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,275 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 skills, from other repositories
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.
hermes-dream
Nightly memory consolidation skill for Hermes agents (Appie-3 & Appie-4). Consolidates memory each night, writes to /hermes-dreams/, and delivers to fleet. Schedule: 03:10 AM daily via Hermes cron.