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/cass-2003/local-workflow-skill/auth-access-controlnpx skills add cass-2003/local-workflow-skill --skill auth-access-controlgit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/auth-access-control)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/auth-access-control"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/auth-access-control.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.00098 | $0.00788 |
| Opus 5 | $0.00049 | $0.00394 |
| Sonnet 5 | $0.00020 | $0.00158 |
| Haiku 4.5 | $0.00010 | $0.00079 |
Grade A, and why
auth-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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth And Access Control
Separate The Concepts
- Authentication answers: who are you?
- Authorization answers: what are you allowed to do?
- Tenant isolation answers: which data boundary applies?
- Audit answers: who did what, when, from where, and why was it allowed?
Do not mix these checks into one vague middleware.
Workflow
- Identify identities: user, service account, API key, webhook sender, admin, anonymous visitor.
- Identify resources: project, workspace, organization, file, invoice, user profile.
- Define actions: read, create, update, delete, approve, export, invite, impersonate.
- Choose model: RBAC, ABAC, ReBAC, or a hybrid.
- Decide enforcement points: route, service, query, storage, background job.
- Add denial defaults, audit logs, tests, and migration path.
Model Selection
| Model | Use When | Warning |
|---|---|---|
| RBAC | roles map cleanly to permissions | role explosion |
| ABAC | context matters: tenant, owner, status, region | policies get hard to debug |
| ReBAC | relationship graph matters: org/team/shared file | needs careful query design |
| ACL | small resource-specific grants | can become scattered |
Enforcement Rules
- Deny by default.
- Check tenant boundary before object access.
- Do not rely only on frontend hiding.
- Put critical authorization in backend service/domain layer.
- Keep policy decisions testable and named.
- Use database constraints or scoped queries for tenant isolation when possible.
- Log privileged actions and authorization failures.
Token And Session Guidance
- Prefer secure, httpOnly, SameSite cookies for browser sessions unless API constraints require bearer tokens.
- Keep access tokens short-lived.
- Rotate refresh tokens and detect reuse for high-risk systems.
- Store only token hashes when persistence is required.
- Never put secrets in localStorage for high-risk apps.
- Validate issuer, audience, expiration, signature, and algorithm for JWTs.
- Do not accept
alg=none.
Multi-Tenant Guardrail
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 · 96 lines · 98 tokens per session scan A ecc502206bd5
auth-access-control is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 788 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…