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 commands/the-17/agentsecrets/logoutgit clone --depth 1 https://github.com/The-17/agentsecretsWhat 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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
logout 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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets logout
Clear your session and remove cached credentials from this machine.
Usage
agentsecrets logout
Description
logout terminates your session on the current machine and wipes all locally cached credentials. It does not affect other machines, team members, or your stored secrets, only the local session.
What Gets Cleared
logout operates in three steps:
1. Remote invalidation (best-effort)
Sends a POST to auth.logout. If the server is reachable, it invalidates the refresh token, preventing it from being used to generate new access tokens. If the server is unreachable (offline, network issue), logout still proceeds locally.
2. OS keychain purge
Removes the private key from the OS keychain:
- macOS: deletes the Keychain entry
- Windows: removes the Credential Manager entry
- Linux: removes the Secret Service entry
3. Config wipe
Clears ~/.agentsecrets/config.json of:
- JWT access and refresh tokens
- Cached workspace keys
- User email and workspace bindings
What Is NOT Cleared
.agentsecrets/project.jsonin any project directory — your project links remain intact. Logging back in and runningagentsecrets secrets pullrestores everything immediately.- Secrets in the OS keychain — secret values stored by
secrets pull(keyed by project ID) are not removed. They remain available foragentsecrets enveven after logout, until they are explicitly deleted withagentsecrets secrets delete. - Remote data — your secrets, workspace, and team remain on the server, encrypted.
When to Use
# Switching to a different account
agentsecrets logout
agentsecrets login # or agentsecrets init for a new account
# Shared machine — end of session
agentsecrets logout
# After a credential-related security incident
agentsecrets logout
# Then rotate the affected secrets:
agentsecrets secrets set COMPROMISED_KEY=new_value
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.
- 2d ago First seen · 74 lines · 0 tokens per session scan A f26d4c1594bd
logout is a command published in the GitHub repository The-17/agentsecrets (172 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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-30.
Other commands, from other repositories
nyxid-connect
Connect a catalog service through NyxID without placing its credential in the agent context.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.