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 UnboundCompute/security-agent-skills --skill auditing-sso-logout-and-session-revocationgit clone --depth 1 https://github.com/UnboundCompute/security-agent-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/unboundcompute/security-agent-skills/auditing-sso-logout-and-session-revocation)<a href="https://agentmods.dev/skills/unboundcompute/security-agent-skills/auditing-sso-logout-and-session-revocation"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-sso-logout-and-session-revocation/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/unboundcompute/security-agent-skills/auditing-sso-logout-and-session-revocation"><img src="https://agentmods.dev/badge/skills/unboundcompute/security-agent-skills/auditing-sso-logout-and-session-revocation.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.00207 | $0.02246 |
| Opus 5.5 | $0.00083 | $0.00898 |
| Sonnet 5.5 | $0.00041 | $0.00449 |
| Haiku 4.5 | $0.00021 | $0.00225 |
Grade A, and why
auditing-sso-logout-and-session-revocation 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing SSO logout and session revocation: ending a session at one place must end it everywhere
Single sign-on spreads one login across many applications, and the hard part is not the login, it is the logout. When a user signs out, an admin disables an account, a password is reset, or the identity provider ends a session, every downstream session and token that login created is supposed to stop working, and often several of them do not. A logout that clears only the local application cookie leaves the identity-provider session alive, so the next visit signs the user back in silently and the logout was cosmetic. A single-logout flow the application never implements means signing out at the identity provider leaves every relying application still logged in. An access or refresh token minted during the session keeps working after logout or after the account is disabled, because nothing revokes it. A session that survives a password reset lets a stolen session outlive the credential change meant to shut it out. And a back-channel logout notification the application does not process is an ended session the application never hears about. The audit ends a session by every available means, user logout, identity-provider logout, admin disable, password reset, token revocation, and then checks that every downstream session and token is actually dead. You audit this by logging out one way and trying to keep using the session another.
When to use
- Users sign in through SSO (SAML or OIDC) across one or more relying applications, and log out through the application, the identity provider, or an admin action.
- Logout may clear only the local session, single logout may be unimplemented, or tokens may outlive the event meant to end them.
- A session may survive a password reset, an account disable, or a deprovisioning event.
Scope check
Test logout and revocation only against applications and identity providers you own or are authorized to assess, with test accounts. Exercising logout, account disable, and password reset changes real session and account state, so use test identities and never disable, reset, or revoke access for accounts that are not yours. If you can't name the authorization, stop.
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.
- 1mo ago First seen · 147 lines · 207 tokens per session scan A 23b1b5fd3fc5
auditing-sso-logout-and-session-revocation is a skill published in the GitHub repository UnboundCompute/security-agent-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 207 tokens to every session and 2,246 once invoked, about $0.0008 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-09-05.
Other skills, from other repositories
prodcheck-review
Review this codebase against the prodcheck pre-production checklists — security, performance, scale, integrations, post-launch readiness and people. Use when asked to check whether a project is ready to ship, to audit an area before launch, or to work through a specific checklist. Produces evidence with file:line…
integrate-arcjet-guard-genkit
Integrate Arcjet security into a Genkit JS agent using @arcjet/guard — wrap ai.defineTool, put guardMiddleware on generate({ use }) for unwrapped / MCP / filesystem tools, and read a caller-owned id from generate({ context }). Use when asked to add Arcjet to genkit, rate limit its tools, screen inbound messages, or…
integrate-arcjet-guard-tanstack-ai
Integrate Arcjet security into a TanStack AI chat() app using @arcjet/guard — put guardMiddleware first on chat({ middleware }) so onBeforeToolCall gates tools, and read a caller-owned id from chat({ context }). Use when asked to add Arcjet to TanStack AI, rate limit its tools, screen inbound messages, or block prompt…
integrate-arcjet-guard-claude-managed-agents
Integrate Arcjet security into Claude Managed Agents (hosted REST+SSE, beta managed-agents-2026-04-01) using @arcjet/guard — screen user.message / initialevents before sessions.events.send, and gate custom tools on agent.customtooluse. Use when asked to add Arcjet to Claude Managed Agents, rate limit custom tools, or…
linear-claude-skill
Manage Linear issues, projects, and teams.
varlock-claude-skill
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits.