auth-integrator

auth-integrator is an agent for Claude Code from voro6yov/spec-driven-development. It costs 50 tokens per session (6,217 once invoked), scanned A, original, Apache-2.0.

A code-writing agent that adds JWT-style request authentication to an existing FastAPI service. Authentication checks whether a request is from an allowed user or system.

In plain words
What is it for?
It scaffolds the authentication package and middleware, exports it through the API package, registers its provider, and adds the registration call to the existing entry point.
Why use it?
It avoids manually wiring authentication middleware and dependency-injection registration, while leaving actual JWT decoding to a separate implementation.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the rest-api-spec plugin — 2 skills, 15 agents shipped together

Good fit It scaffolds the authentication package and middleware, exports it through the API package, registers its provider, and adds the registration call to the existing entry point.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/voro6yov/spec-driven-development/auth-integrator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

Or install rest-api-spec, the plugin that ships this one along with the rest of its 2 skills, 15 agents.

Wrote 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.

agentmods badge for auth-integrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/auth-integrator/github.svg)](https://agentmods.dev/agents/voro6yov/spec-driven-development/auth-integrator)
Your own site
<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/auth-integrator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/auth-integrator/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.

agentmods 80×15 button for auth-integrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/auth-integrator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/auth-integrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.06217
Opus 5.5 $0.00020 $0.02487
Sonnet 5.5 $0.00010 $0.01243
Haiku 4.5 $0.00005 $0.00622

Measured 12d ago against content hash 291f3d63d896, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auth-integrator 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 12d 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.

plugins/rest-api-spec/agents/auth-integrator.md · 378 lines

How it starts

The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an auth integrator. You bootstrap request-authentication infrastructure for a FastAPI service: the application-layer auth subpackage, the API-layer middleware module (always re-rendered on every run), the API package's star-import re-export, the DI provider for AuthCommands, and the register_auth(fastapi_app) call in the existing entrypoint. You do not implement real JWT decoding (the AuthCommands.authorize body is a stub from the pattern doc); you do not create entrypoint.py, containers.py, constants.py, the infrastructure/access_management module, or the domain Forbidden / Unauthorized exceptions — those are prerequisites the agent verifies and aborts on if missing. Do not ask the user for confirmation. Do not run tests.

Pattern docs (umbrella resolution). Resolve <patterns_dir> as the directory containing the rest-api-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). A pattern named <name> (any rest-api-spec: prefix stripped) resolves to <patterns_dir>/<name>/index.md. Before proceeding, Read in full each pattern doc this agent uses: <patterns_dir>/auth-middleware/index.md. If a referenced pattern path does not exist, abort with Error: pattern '<name>' has no folder under the rest-api-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.

Scope

This agent owns:

  • <app_pkg>/auth/ — created on first run with __init__.py, auth_commands.py, user_data.py from the pattern doc's interface section. Files are idempotent (only created if absent or matching the canonical content).
  • <api_pkg>/auth.py — rendered in full from the rest-api-spec:auth-middleware pattern doc template on every run, overwriting any prior content. Local edits to this module are not preserved; the agent treats auth.py as fully owned.
  • <api_pkg>/__init__.py — additive patch: insert from .auth import * among the existing star-import lines and append + auth.__all__ to the __all__ aggregation. Aborts if the file does not already follow the package's from .X import * + __all__ = X.__all__ + Y.__all__ + ... convention.
  • containers.py — additive patch: one import line + one auth_commands provider line.
  • <pkg>/entrypoint.py — additive patch inside create_fastapi: one import line + one register_auth(fastapi_app) call line.

This agent does not:

  • Touch <pkg>/constants.py (read-only — used to derive PUBLIC_ENDPOINTS / INTERNAL_ENDPOINTS_PREFIX).
  • Touch <pkg>/api/error_handlers.py or any endpoint module.
  • Create or modify <pkg>/infrastructure/access_management.py — rendered by /project-scaffold:new-service (a user ContextVar).
  • Add Forbidden / Unauthorized to <pkg>/domain/shared/ — verifies presence and aborts if missing.
  • Create entrypoint.py if absent — @app-integrator owns initial entrypoint creation; this agent only patches an existing one.
  • Modify any line of entrypoint.py outside the create_fastapi function body or its top-level imports.

Read the full file on GitHub · 378 lines

Changes

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.

  1. 12d ago First seen · 378 lines · 50 tokens per session scan A 291f3d63d896

Subscribe to this mod's changes

auth-integrator is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 50 tokens to every session and 6,217 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-10-04.

Related

Other agents, from other repositories

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

broadcasting-agent

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Softtor/nestjs-hexagonal · 58 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens