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/proticom/gnosys/projectsgit clone --depth 1 https://github.com/proticom/gnosysWhat 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.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
projects 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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys projects
List registered projects from the central DB, with optional pruning of dead entries.
Usage
gnosys projects
gnosys projects --json
gnosys projects --all
gnosys projects --prune --dry-run
gnosys projects --prune --yes
Options
| Option | Description |
|---|---|
--json |
Output as JSON |
--all |
Include dead projects (deleted directories) and projects not on this machine |
--prune |
Delete registry entries whose directory no longer exists |
--dry-run |
With --prune: list what would be deleted without deleting |
--yes |
With --prune: skip the confirmation prompt |
Behavior
- Opens the central DB via
GnosysDB.openCentral(). - Loads all projects with
centralDb.getAllProjects(). - Resolves each project's path for this machine via
readMachineConfig()andeffectiveProjectPath(). - Normal listing (default): shows live projects on this machine; hides dead or absent paths unless
--all. --prune: finds dead projects, shows them, optionally confirms, then callscentralDb.deleteProject(p.id).
Output modes
Human listing shows project name, ID, resolved directory, memory count, and created date.
JSON listing includes count, totalRegistered, deadCount, and projects.
Prune JSON includes deleted, remaining, and deletedProjects.
Empty registry:
No projects registered. Run 'gnosys init' in a project directory.
No live projects:
No live projects (N dead — run 'gnosys projects --all' to see them or 'gnosys projects --prune' to remove them).
Errors
Central DB unavailable:
Central DB not available (better-sqlite3 missing).
Other errors:
Error: <message>
Failure paths set process.exitCode = 1 and return through finally so the DB handle is closed.
Validation
cd gnosys-public
npm run cli -- projects --help
npx vitest run src/test/projects-command-handler.test.ts
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.
- yesterday First seen · 81 lines · 0 tokens per session scan A 753ef3bad12e
projects is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 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-31.
Other commands, from other repositories
init-project
Configure this project for Obsidian PKM — connects the repo to a vault project folder and writes CLAUDE.md integration directives.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
competitive-landscape
Map the competitive landscape for a market or company.