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 BreadchainCoop/labor.fun --skill access-controlgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/access-control)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/access-control"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/access-control/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/access-control"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/access-control.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00472 |
| Opus 5.5 | $0.00015 | $0.00189 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
access-control 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 1mo 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
/access-control — Permission Check & Reference
Quick-reference for Breadbrich Engels's access control. Use when checking whether the caller can perform an action.
Two States
| State | Who | What they can do |
|---|---|---|
| Allowlisted user | Anyone with a sender_context (a KB people file + identity mapping) |
Full read/write everywhere; cross-channel; manage tasks/groups; approve expenses |
| Unknown sender | No KB identity mapping | Open-visibility reads only; no writes; no actions |
That's the whole model. There are no Admin/Coordinator/Contributor/Guest tiers, and tags: on people files are descriptive labels only (no permission effect).
Visibility Frontmatter Still Applies
Per-document visibility: controls what gets shown, not whether the user has write access:
| Level | Surfacing rule |
|---|---|
open |
Safe in summaries and shared replies |
restricted |
Surface only on direct request; not in summaries |
private |
Surface only to the document's created_by or on explicit direct request, never in a shared channel without confirmation |
Quick Permission Check Flow
- Identify the requester →
rules/identity/README.md - If they resolved to a KB person → allowlisted → action permitted
- Before surfacing a document, check its
visibilityfrontmatter
Group-level isMain
isMain is a property of a registered chat (the "control channel"). It is not a permission gate — an allowlisted user can do main-group operations from any registered group.
Special Surfacing Rules
- WTF List entries: always anonymous; never record submitter identity
- People profiles: private by default — don't proactively surface in channels; prefer DMs
Related
- Full rules:
/workspace/project/rules/access-control/ - Identity resolution:
/workspace/project/rules/identity/ - Privacy policy:
/workspace/project/rules/access-control/privacy-policy.md
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.
- 1mo ago First seen · 49 lines · 37 tokens per session scan A 81746a172557
access-control is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…