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/projectgit 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.01274 |
| Opus 5 | $0.00000 | $0.00637 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
project 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets project
Create, link, and manage projects within the active workspace.
Subcommands
agentsecrets project list
agentsecrets project create <name>
agentsecrets project use <project-id-or-name>
agentsecrets project update <name>
agentsecrets project delete <name>
agentsecrets project invite <email>
Overview
A project maps to an application or service. Secrets are partitioned by project — my-backend, mobile-app, and infra can each have their own set of credentials.
Projects live inside workspaces. The active workspace determines which projects you can see and interact with.
When you run any agentsecrets secrets command, it reads the project context from .agentsecrets/project.json in the current directory.
project list
agentsecrets project list
Lists all projects in the active workspace:
NAME ID CREATED
→ my-backend proj_abc123 2026-01-15
mobile-app proj_def456 2026-02-01
infra proj_ghi789 2026-02-20
The → marks the project linked to the current directory (from .agentsecrets/project.json), if any.
project create
agentsecrets project create my-backend
Creates a new project in the active workspace and links the current directory to it by writing .agentsecrets/project.json.
After this command:
agentsecrets status
# Project: my-backend (proj_abc123)
# Workspace: My Team (ws_xyz789)
# Storage: Keychain
One project per directory — running project create or project use in a directory overwrites the existing .agentsecrets/project.json.
project use
agentsecrets project use my-backend
Links the current directory to an existing remote project. Writes .agentsecrets/project.json.
Use this when:
- A teammate created the project and you want to link your local directory to it
- You're switching a directory to a different project
- You cloned a repo that already has
.agentsecrets/project.jsonand need to re-link
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 · 183 lines · 0 tokens per session scan A 9c93a796cd95
project 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,274 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.