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/add-structuredgit 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.00621 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
add-structured 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys add-structured
Add a memory with explicit structured fields — no LLM structuring step.
Usage
gnosys add-structured --title "Decision" --category decisions --content "Use SQLite as source of truth"
gnosys add-structured --title "Preference" --category preferences --content "Use concise reviews" --user
gnosys add-structured --title "Org policy" --category policies --content "Shared guidance" --global
gnosys add-structured --title "Tagged" --category notes --content "Tagged content" --tags '{"domain":["cli"],"type":["note"]}'
Required options
| Option | Description |
|---|---|
--title <title> |
Memory title |
--category <category> |
Category directory name (e.g. decisions, preferences) |
--content <content> |
Memory body as markdown |
Optional options
| Option | Description |
|---|---|
--tags <json> |
Tags as JSON object (default {}) |
--relevance <keywords> |
Keyword cloud for discovery (defaults to content snippet) |
-a, --author <author> |
Author (default human) |
--authority <authority> |
Authority level (default declared) |
--confidence <n> |
Confidence 0–1 (default 0.8) |
-s, --store <store> |
Target store hint |
--user |
Store as user-scoped memory (scope: user) |
--global |
Store as global-scoped memory (scope: global) |
Behavior
User or global scope (--user / --global)
- Writes directly to the central DB.
--global:scope: global, no project id.--user:scope: user, includes project id when available.- Prints
Memory added (scope: user|global): <title>and ID.
Default project scope
- Parses
--tagsas JSON; exits withInvalid --tags JSON. Example: '{"domain":["auth"],"type":["decision"]}'on parse failure. - Generates category-scoped ID via central DB.
- Inserts project-scoped memory (
scope: project). - Prints
Memory added: <title>and ID.
Output example
Memory added: Decision: use SQLite
ID: deci-042
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 · 75 lines · 0 tokens per session scan A c98e67e90b84
add-structured 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 621 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.