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 settings/kbwen/agent-virtual-office/settingsgit clone --depth 1 https://github.com/KbWen/agent-virtual-officeGrade A, and why
agent-virtual-office 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 2d 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.
What it actually says
{
"hooks": {
"UserPromptSubmit": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"PreToolUse": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"PostToolUse": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"SubagentStart": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"SubagentStop": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"PermissionDenied": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
],
"StopFailure": [
{
"hooks": [
{
"type": "command",
"command": "node public/hooks/office-status-hook.js"
}
]
}
]
}
}
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.
- 2d ago First seen · 85 lines scan A 236308a20a82
agent-virtual-office is a settings file published in the GitHub repository KbWen/agent-virtual-office (11 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other settings, from other repositories
agent-layer
Agent settings declaring 4 allowed tools.
nextjs-template-mongodb
Agent settings configuring enabledPlugins.
settings
Agent settings declaring 2 hook events (PreToolUse, PostToolUse).
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.