Borrowing it
Nothing to install: this file belongs to extra-org/extra. 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/extra-org/extra/main/.claude/skills/sidecar-auth-context/SKILL.mdgit clone --depth 1 https://github.com/extra-org/extraWrote 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/extra-org/extra/sidecar-auth-context)<a href="https://agentmods.dev/skills/extra-org/extra/sidecar-auth-context"><img src="https://agentmods.dev/badge/skills/extra-org/extra/sidecar-auth-context/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/extra-org/extra/sidecar-auth-context"><img src="https://agentmods.dev/badge/skills/extra-org/extra/sidecar-auth-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 32 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00041 | $0.00486 |
| Opus 5.5 | $0.00016 | $0.00194 |
| Sonnet 5.5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
sidecar-auth-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 2mo 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
Skill: Plugin Context & Access
When to use this skill
Use this when working on resolver plugins, the fixed access plugin contract,
mapping resolver outputs into ExecutionContext, or protected-node filtering.
Primary task: tasks/0006-sidecar-auth-context.md.
Files to read first
AGENTS.mddocs/SIDECAR_CONTEXT_AUTH.mddocs/ARCHITECTURE.mddocs/PROMPT_RENDERING.md
Architecture rules
- The runtime contains no customer-specific auth/business logic.
- Resolver plugins fill prompt variables before a node runs.
- Tool plugins are separate and run during LLM execution.
- Protected nodes are hidden from routers unless the access plugin allows them.
- Access failures fail closed.
- Secrets are redacted in traces.
Implementation rules
- Implement plugin integration in
src/agentplatform/context. - Build
ctxfrom request headers and request data. - Call resolver plugin methods declared in top-level
resolvers. - If any node has
protected: true, requireplugins/access.pywithAccessResolver.can_access(ctx, node_id) -> bool. - Keep plugin instances shared where appropriate; keep request data on
ExecutionContext.
Validation checklist
- No customer-specific logic in the runtime.
- Resolver outputs are request-scoped.
- Protected nodes are filtered before routing.
- Deny/error cases fail closed and are traced.
- Secrets redacted in traces.
- Tests use fake plugins covering allow/deny/error.
-
make checkpasses.
Common mistakes to avoid
- Implementing auth/tenant/business rules inside the engine.
- Failing open when access plugin raises.
- Exposing resolver plugins to the LLM as tools.
- Logging raw tokens/secrets in the trace.
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.
- 2mo ago First seen · 64 lines · 41 tokens per session scan A 1fefbee9299b
sidecar-auth-context is a skill published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 486 once invoked, about $0.0002 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-30.
Other skills, from other repositories
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.
argent-tv-interact
Control and inspect TV apps via argent, Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
06-product-brief
Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.
issue-resolve
Use when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix. Mutating and gated: it works in an isolated worktree, fixes test-first, and opens a DRAFT PR for human review. Built to run autonomously (hermes-ops) within a strict action envelope…