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/n-n-code/n-n-code-skills/security-identity-accessnpx skills add n-n-code/n-n-code-skills --skill security-identity-accessgit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/security-identity-access)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/security-identity-access"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/security-identity-access.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 | $0.00080 | $0.01243 |
| Opus 5 | $0.00040 | $0.00622 |
| Sonnet 5 | $0.00016 | $0.00249 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
security-identity-access 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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Identity Access
Use this companion only with security. If security is not applicable, do
not apply this overlay.
Composition Contract
security remains primary and owns investigation authority, attacker and trust
boundary analysis, evidence outcomes, severity and confidence, remediation,
validation, and report shape.
This companion owns identity-specific state and transition modeling, authentication and session invariants, recovery and federation risks, tenant authorization, and routing to selectively needed identity detail. Matching backend and language skills still own ordinary implementation mechanics.
Model The Identity Boundary
Map the repository's actual objects and names. Do not invent states merely to fit this model.
| Object | State or binding to establish |
|---|---|
| principal or account | lifecycle state and usable identifiers |
| authenticator or factor | pending, bound, active, replaced, lost, or revoked |
| transaction or capability | purpose, subject, initiating context, expiry, and unused or consumed state when one-time |
| session or token | principal, authentication event, issue time, expiry, rotation, and revocation |
| membership or grant | principal, tenant, role or capability, resource scope, and lifecycle state |
| external identity | trusted issuer or security domain plus its stable subject identifier |
For every security-relevant transition, establish as applicable:
- who or what may initiate it
- which authenticated, verified, or recent state it requires
- which principal, purpose, transaction, client, tenant, and destination it is bound to
- whether authorization is re-evaluated at use time
- whether consumption and state mutation are atomic
- which sessions, credentials, grants, caches, or notifications it affects
Use these compact invariants:
accepted state-changing transition =
valid actor or proof and authorized transition
and required valid transaction, event, assertion, or capability bindings
and atomic or otherwise replay-safe authoritative mutation
effective authority =
principal, applicable grant or membership, and policy state
are authoritative or sufficiently current for the accepted revocation window
and target action/resource is within server-authorized scope
What ships with it
4 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.
- 4d ago First seen · 124 lines · 80 tokens per session scan A 8966a5fb6b5c
security-identity-access is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 7d ago), licensed MIT. It adds 80 tokens to every session and 1,243 once invoked, about $0.0004 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
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
loop-review-fold
Run the simple review-change/fold-findings loop for an open feature or fix unit. Inspect persisted review evidence first so a previous review resumes with fold-findings instead of reviewing the same candidate again. Unresolved findings go to triage-issue with an immediate-fix instruction; oversized findings become a…
plan-feature-from-issue
Internal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC product half (capability closure satisfied) with Closes #N traceability.
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".