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/import-projectgit 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.00532 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
import-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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys import project
Restore a portable .json.gz project bundle created by gnosys export project into the central DB.
Usage
gnosys import project ./my-project.gnosys.json.gz
gnosys import project ./bundle.gnosys.json.gz --strategy replace
gnosys import project ./bundle.gnosys.json.gz --working-directory /path/to/project --json
Options
| Option | Description |
|---|---|
--strategy <strategy> |
Conflict handling: merge (default), replace, or new-id |
--working-directory <dir> |
Override the bundle's working_directory (e.g. when restoring on a different machine) |
--json |
Output the result as JSON |
Behavior
- Validates
--strategybefore opening the central DB. - Opens the central DB via
GnosysDB.openCentral(). - Resolves
bundlePathwithpath.resolve(). - Calls
importProject(centralDb, { bundlePath, strategy, workingDirectoryOverride }). - Prints human summary or JSON.
- Closes central DB in
finally.
Human output
Imported project my-project (my-project)
Strategy: merge
Memories: 42 inserted, 3 skipped, 0 replaced
Relationships: 12
Audit entries: 88
JSON output
Full importProject result object when --json is set.
Errors
Invalid strategy (validated before DB open):
Invalid strategy: foo. Use one of: merge, replace, new-id
Central DB unavailable:
Central DB unavailable.
Import failures (malformed bundle, unsupported version, etc.):
Import failed: <message>
Failure paths use process.exitCode = 1 and close the DB in finally.
Validation
cd gnosys-public
npm run cli -- import project --help
npx vitest run src/test/import-project-command-handler.test.ts
node scripts/audit-commands.mjs --write
Related commands
gnosys import— parent command (bulk CSV/JSON/JSONL import).gnosys export project— create a portable project bundle.gnosys export vault— Obsidian markdown vault export.
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 · 80 lines · 0 tokens per session scan A da1268fb4027
import-project is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 532 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.