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/ingestgit 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.00638 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
ingest 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 ingest
Ingest a local file (PDF, DOCX, TXT, MD, etc.) into Gnosys memory. Extracts text, splits into chunks, and creates atomic memories.
Usage
gnosys ingest ./notes.md
gnosys ingest ./whitepaper.pdf --mode llm --store project
gnosys ingest ./notes.txt --mode structured --dry-run
gnosys ingest ignored --list-attachments --store project
gnosys ingest notes.md --directory /path/to/project
Options
| Option | Description |
|---|---|
--mode <mode> |
Ingestion mode: llm (default) or structured |
-s, --store <store> |
Target store: project, personal, or global |
-a, --author <author> |
Author (default human) |
--authority <authority> |
Authority level (default imported) |
--dry-run |
Preview without writing memories |
--list-attachments |
List stored attachments instead of ingesting |
-d, --directory <dir> |
Base directory for resolving the file path |
Behavior
File ingestion (default)
- The
<fileOrGlob>argument is resolved as a single local path relative to--directoryor the current working directory. Despite the argument name, glob expansion is not performed in the current CLI implementation. - Exits with
File not found: <path>when the resolved path does not exist. - Requires a writable store; exits with
No writable store found...otherwise. - Runs
ingestFilewith progress output, then prints file type, attachment info, duration, created memories (with paths), and chunk errors.
List attachments (--list-attachments)
- Ignores the file argument for ingestion purposes.
- Lists attachments in the writable store: name, size, UUID, hash prefix, linked memory IDs, created date.
- Prints
No attachments found.when empty.
Output example
Ingesting: whitepaper.pdf
File type: pdf
Attachment: whitepaper.pdf (a1b2c3d4...)
Duration: 12.3s
Memories created: 5
Memories:
memo-001: Introduction [page 1]
Path: ...
Platform notes
macOS / Linux
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 84231b243673
ingest 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 638 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.