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/workspacegit 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.01314 |
| Opus 5 | $0.00000 | $0.00657 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
workspace 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets workspace
Manage team workspaces — members, roles, and the zero-trust domain allowlist.
Subcommands
agentsecrets workspace list
agentsecrets workspace create <name>
agentsecrets workspace switch [name]
agentsecrets workspace members
agentsecrets workspace invite <email...>
agentsecrets workspace remove <email>
agentsecrets workspace promote <email>
agentsecrets workspace demote <email>
agentsecrets workspace allowlist add <domain> [domain...]
agentsecrets workspace allowlist list
agentsecrets workspace allowlist log
Overview
A workspace is the top-level organizational boundary in AgentSecrets. Think of it as a team or organization. It contains:
- Projects — partitioned sets of secrets (e.g.,
backend,mobile,infra) - Members — users with access to the workspace
- An allowlist — the domains the proxy is allowed to reach
When you create an account, a personal workspace is created automatically. You can create additional shared workspaces for teams.
workspace list
agentsecrets workspace list
Lists all workspaces you have access to. The active workspace is marked with →.
→ My Projects (ws_abc123) personal
Acme Corp (ws_def456) shared
Side Project (ws_ghi789) shared
workspace create
agentsecrets workspace create "Acme Backend Team"
Creates a new shared workspace and immediately switches to it. Any projects created after this point belong to the new workspace.
workspace switch
agentsecrets workspace switch "Acme Backend Team"
agentsecrets workspace switch # interactive picker
Sets the active workspace. All subsequent project and secrets operations operate within the selected workspace. Updates current_workspace_id in ~/.agentsecrets/config.json.
workspace members
agentsecrets workspace members
Lists all members of the current workspace:
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 · 211 lines · 0 tokens per session scan A 69064211fba0
workspace 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 1,314 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.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.