Borrowing it
Nothing to install: this file belongs to KbWen/agent-virtual-office. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KbWen/agent-virtual-office/main/.agents/skills/auth-security/SKILL.mdgit clone --depth 1 https://github.com/KbWen/agent-virtual-officeWrote 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/kbwen/agent-virtual-office/auth-security)<a href="https://agentmods.dev/skills/kbwen/agent-virtual-office/auth-security"><img src="https://agentmods.dev/badge/skills/kbwen/agent-virtual-office/auth-security/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/kbwen/agent-virtual-office/auth-security"><img src="https://agentmods.dev/badge/skills/kbwen/agent-virtual-office/auth-security.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.00018 | $0.01489 |
| Opus 5.5 | $0.00007 | $0.00596 |
| Sonnet 5.5 | $0.00004 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
auth-security 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.
This is a copy
100% identical to auth-security — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth & Security
When to Apply
- Classification: ALL classifications that touch auth, permissions, user data, or session management
- Phase: /plan (auth flow design), /implement (auth logic), /review (MANDATORY for any auth-related change), /test (auth bypass testing)
- Trigger: Task involves login, registration, password, token, session, role, permission, or access control
Relationship to Security Guardrails
This skill extends .agent/rules/security_guardrails.md with APP-specific auth patterns. The security guardrails handle OWASP scanning and secret detection. This skill handles auth architecture and implementation patterns.
Precedence: security_guardrails.md > this skill. If conflict, security guardrails win.
Conventions
Customize after /app-init: Replace these with your project's ADR auth decisions.
Authentication Flow (JWT Example)
Client Server DB
|-- POST /auth/login -->| |
| {email, password} |-- verify password hash -->|
| |<-- user record -----------|
|<-- {access_token, | |
| refresh_token} ---| |
| | |
|-- GET /api/resource ->| |
| Authorization: |-- verify token |
| Bearer <access> |-- check permissions |
|<-- 200 data ---------| |
| | |
|-- POST /auth/refresh->| |
| {refresh_token} |-- verify + rotate ------->|
|<-- {new_access, |<-- new tokens ------------|
| new_refresh} -----| |
Token Rules
- Access token: Short-lived (15-30 min). Stored in memory only (NOT localStorage).
- Refresh token: Longer-lived (7-30 days). Stored in httpOnly, secure, sameSite cookie.
- Token rotation: Issue new refresh token on each refresh. Invalidate old one.
- Revocation: Maintain a blocklist for compromised tokens (or use short expiry + DB check).
What ships with it
1 file 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.
- 1mo ago First seen · 148 lines · 18 tokens per session scan A ad3e61e35cd1
auth-security is a skill published in the GitHub repository KbWen/agent-virtual-office (61 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,489 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to auth-security, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
devtools-vite-plugin
Configure @tanstack/devtools-vite for source inspection (data-tsd-source, inspectHotkey, ignore patterns), console piping (client-to-server, server-to-client, levels), enhanced logging, server event bus (port, host, HTTPS), production stripping (removeDevtoolsOnBuild), editor integration (launch-editor, custom…
devtools-marketplace
Publish plugin to npm and submit to TanStack Devtools Marketplace. PluginMetadata registry format, plugin-registry.ts, pluginImport (importName, type), requires (packageName, minVersion), framework tagging, multi-framework submissions, featured plugins.
devtools-production
Handle devtools in production vs development. removeDevtoolsOnBuild, devDependency vs regular dependency, conditional imports, NoOp plugin variants for tree-shaking, non-Vite production exclusion patterns.
devtools-bidirectional
Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.
devtools-framework-adapters
Use devtools-utils factory functions to create per-framework plugin adapters. createReactPlugin/createSolidPlugin/createVuePlugin/createPreactPlugin, createReactPanel/createSolidPanel/createVuePanel/createPreactPanel. [Plugin, NoOpPlugin] tuple for tree-shaking. DevtoolsPanelProps (theme). Vue uses (name, component)…
devtools-app-setup
Install TanStack Devtools, pick framework adapter (React/Vue/Solid/Preact), register plugins via plugins prop, configure shell (position, hotkeys, theme, hideUntilHover, requireUrlFlag, eventBusConfig). TanStackDevtools component, defaultOpen, localStorage persistence.