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/sourjya/kiro-rails/auth-implementationnpx skills add sourjya/kiro-rails --skill auth-implementationgit clone --depth 1 https://github.com/sourjya/kiro-railsWrote 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/sourjya/kiro-rails/auth-implementation)<a href="https://agentmods.dev/skills/sourjya/kiro-rails/auth-implementation"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/auth-implementation.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.1 | $0.00042 | $0.00599 |
| Opus 5 | $0.00021 | $0.00300 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
auth-implementation 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 6d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Implementation Checklist
When implementing any authentication flow, ALL of the following paths must be handled. Do not implement only the happy path.
Mandatory Paths
1. Happy Path
- User has valid session → proceed normally
- User authenticates successfully → redirect to intended destination
2. Expired Token
- Access token expired → attempt silent refresh with refresh token
- Refresh token expired → redirect to login (not infinite loop)
- Never fire API requests before confirming token is available
3. Missing Session
- No token in storage → show login UI or redirect to identity provider
- Don't auto-redirect without checking if a session exists first
4. Redirect Loop Prevention
- Max 2 redirects then show an error page with clear message
- Store redirect count in sessionStorage, reset on successful auth
- Never redirect from login page back to login page
5. Provider-Specific Quirks
- Cognito: does NOT support
prompt=nonefor silent auth - Keycloak: supports
prompt=nonebut returnslogin_requirederror if no session - Auth0: supports silent auth via
/authorizewithprompt=none - Always check provider documentation for supported parameters
6. Graceful Degradation
- If identity provider is unreachable → show error, don't crash the app
- If OIDC discovery endpoint fails → fall back to manual config or show maintenance page
- Never make the entire app dependent on auth provider availability for rendering
Implementation Rules
redirect_urimust be dynamic - usewindow.location.origin+ callback path. Never hardcodelocalhost.- State parameter - always include a random
stateparam to prevent CSRF. Verify it on callback. - Token storage - access tokens in memory (short-lived), refresh tokens in httpOnly cookies or secure storage. Never localStorage for refresh tokens.
- Logout must clear ALL state - tokens, cached user info, query cache, any auth-dependent state.
- 401 handling - on 401 response, attempt ONE silent refresh. If that fails, redirect to login. Don't retry indefinitely.
- Multi-tab sync - if user logs out in one tab, other tabs should detect it (via storage event or BroadcastChannel).
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.
- 6d ago First seen · 57 lines · 42 tokens per session scan A d88e8a9315fa
auth-implementation is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 599 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…