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/importgit 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.00548 |
| Opus 5 | $0.00000 | $0.00274 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
import 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys import
Bulk-import CSV, JSON, or JSONL data into Gnosys memories. Also serves as the parent command for project bundle import.
Usage (bulk import)
gnosys import data.csv --format csv --mapping '{"name":"title","body":"content"}'
gnosys import records.json --format json --mapping '{"title":"title","text":"content"}' --dry-run
gnosys import records.jsonl --format jsonl --mapping '{"title":"title","body":"content"}' --mode structured --store project
Usage (project bundle)
gnosys import project bundle.json.gz
See the import project leaf command docs for bundle restore options (--strategy, --working-directory, etc.).
Bulk import options
| Option | Description |
|---|---|
--format <format> |
Required: csv, json, or jsonl |
--mapping <json> |
Required field mapping JSON |
--mode <mode> |
llm or structured (default structured) |
--limit <n> |
Max records to import |
--offset <n> |
Skip first N records |
--skip-existing |
Skip records whose titles already exist |
--batch-commit / --no-batch-commit |
Single vs per-record commits (default batch) |
--concurrency <n> |
Parallel LLM calls (default 5) |
--dry-run |
Preview without writing |
--store <store> |
Target store (default project) |
Behavior
- Without
fileOrUrl, prints usage for bulk and project paths and exits. - Bulk import requires
--formatand--mapping; otherwise exits with a clear error pointing toimport projectfor bundles. - Invalid mapping JSON exits with example message.
- Resolves writable store, loads tag registry, runs
performImportwith progress bar on stderr. - After successful import (non-dry-run), reindexes search when records were imported.
- Prints summary via
formatImportSummary(prefixedDRY RUN —or✓).
Mapping targets
Valid mapping targets: title, category, content, tags, relevance.
Validation
cd gnosys-public
npm run cli -- import --help
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 · 60 lines · 0 tokens per session scan A 2d7cf68af8c0
import 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 548 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.
build
Run full verification pipeline.
generate-rules
Generate development rules and standards into RULES.md.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.
prd
Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.