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 jeet129/praxis --skill authn-authzgit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/authn-authz)<a href="https://agentmods.dev/skills/jeet129/praxis/authn-authz"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/authn-authz/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/jeet129/praxis/authn-authz"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/authn-authz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
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 →
- high Privilege Escalation · line 61 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 169 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 90 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 96 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 168 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 143 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00137 | $0.03076 |
| Opus 5 | $0.00068 | $0.01538 |
| Sonnet 5 | $0.00027 | $0.00615 |
| Haiku 4.5 | $0.00014 | $0.00308 |
Grade A, and why
authn-authz 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 8d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authentication & Authorization
capability: quality-and-security
domain: cross-cutting
state: active
dependencies:
- secure-coding
- secrets-config
- threat-modeling
triggers:
- "designing the identity model for a new project"
- "choosing authn protocol (OIDC / OAuth2 / SAML / passwordless)"
- "implementing or revising authorization rules (RBAC / ABAC / ReBAC)"
- "wiring service-to-service auth (mTLS / workload identity)"
- "auditing endpoint authorization for BOLA / IDOR"
- "designing token rotation + revocation"
outputs:
- identity model document (who can access what, via which mechanism)
- authn protocol choice + integration design (per identity provider)
- authz policy model (RBAC / ABAC / ReBAC) with code-level enforcement plan
- token lifecycle (issuance / refresh / revocation / rotation cadence)
- service-to-service auth design (mTLS / workload identity / signed tokens)
- object-level authorization checklist per endpoint
consumers:
- solution-architect (designs identity + authz)
- backend-developer (implements via active stack pack)
- frontend-developer (consumes for auth flows)
- security-reviewer (audits placement)
- multi-tenancy (consumes tenant-aware authz)
- compliance-privacy (consumes for audit-log requirements)
references: []
Two concerns the team must not conflate. Authentication = who you are. Authorization = what you can do. Wrong authn lets the wrong identity in; wrong authz lets the right identity do the wrong things.
The principle: default deny; explicit allow; check at every layer that crosses a trust boundary.
When this skill fires
- A new project's identity model is being designed.
- A protocol choice is being made (OIDC / OAuth2 / SAML / passwordless).
- New authorization rules are being added (a new role, a new permission, a new resource type).
- Service-to-service auth is being wired (mTLS, signed tokens, workload identity).
- A PR introduces a new authenticated endpoint — the authz model is reviewed.
- An audit surfaces missing or incorrect authorization (BOLA / IDOR is the most common API security failure).
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.
- 8d ago First seen · 250 lines · 137 tokens per session scan A 704ac5d1f1b7
authn-authz is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 4d ago), licensed MIT. It adds 137 tokens to every session and 3,076 once invoked, about $0.0007 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…