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 skills add Eliyce/paqad-ai --skill auth-mechanism-reviewgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/auth-mechanism-review)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/auth-mechanism-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/auth-mechanism-review/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/eliyce/paqad-ai/auth-mechanism-review"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/auth-mechanism-review.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.00035 | $0.01028 |
| Opus 5 | $0.00017 | $0.00514 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
auth-mechanism-review 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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What It Does
Reviews authentication implementation for weaknesses that let an attacker bypass identity verification — JWT algorithm confusion, session fixation, OAuth redirect manipulation, brute-force surfaces, and weak password storage — producing findings backed by code or test evidence.
Use This When
Use this when module docs or route inventories describe login flows, session management, token issuance/validation, OAuth/OIDC callbacks, password reset flows, or MFA enforcement.
Inputs
- Read the module docs describing authentication and session flows.
- Read
references/auth-attack-checklist.mdbefore evaluating each area. - Read code files and tests that show JWT validation, session handling, and rate limiting.
Procedure
-
JWT review: Find JWT validation code. Check:
- Algorithm is verified;
alg:noneis explicitly rejected - RS256 public key is not reused as HMAC secret (RS256 → HS256 confusion attack)
- Token expiry (
exp) is enforced; refresh token rotation is implemented kidheader is not used in a file path or SQL lookup without sanitization- JWT secret is not a weak/guessable string (
secret,password,key,123456) audandissclaims are validated
- Algorithm is verified;
-
Session review: Check:
- Session fixation protection: session ID is regenerated after successful authentication
Secure+HttpOnly+SameSite=Strictcookie flags- Session invalidation on both logout and password change
- Absolute session timeout (not just sliding window)
-
Token storage: Find client-side token storage.
localStorageorsessionStorageare accessible to XSS;HttpOnlycookies are not. Verify refresh tokens are stored separately from access tokens. Check that a token revocation mechanism exists. -
Brute-force protection: Find login, password reset, and OTP verification endpoints. Check for:
- Per-IP or per-account rate limiting
- Account lockout after N failures
- Username enumeration via response timing or different error messages ("user not found" vs "wrong password")
What ships with it
6 files 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.
- 9d ago First seen · 93 lines · 35 tokens per session scan A 327c330fc9f9
auth-mechanism-review is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,028 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-09-03.
Other skills, from other repositories
pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-go
A command that implements code from a SPEC, a document describing the required behavior and work.
auto-plan
A code-planning skill that examines a codebase and creates a detailed specification, implementation plan, and acceptance criteria. It can organize requirements using EARS, a structured way to describe how software should behave in different situations.
agent-pipeline
Multi-agent pipeline orchestration skill.
adaptive-quality
Per-task execution profile selection based on complexity in Balanced quality mode.