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/checkgit 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.00501 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
check 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.
What it actually says
gnosys check
Test LLM connectivity for each configured task route.
Usage
gnosys check
gnosys check --task structuring
gnosys check --task synthesis
gnosys check --task synthesis
gnosys check --task vision
gnosys check --task transcription
gnosys check --task dream
Options
| Option | Description |
|---|---|
-t, --task <name> |
Test only one task instead of all six |
Supported task names
| Task | Purpose |
|---|---|
structuring |
Adding memories, tagging |
synthesis |
Q&A answers (gnosys ask) |
vision |
Images, PDFs |
transcription |
Audio files |
dream |
Overnight consolidation |
Config resolution
- Loads project config from
.gnosys/in the current working directory when it differs from defaults. - Otherwise falls back to global config in
~/.gnosys/. - Prints which config path was used in the header.
Output states
Each task line shows provider/model, then one of:
- ✓ connected —
testConnection()succeeded; latency in ms is shown - ✗ failed — provider unavailable (missing API key) or connection error
- ⚠ disabled — dream task when
dream.enabledis false (skipped, not counted as failure)
Summary line
When all checked tasks pass:
✓ All 5/5 tasks connected.
When some fail:
3/6 connected, 2 failed, 1 skipped.
Fix: Run 'gnosys setup' to configure providers and API keys.
Errors
Unknown --task name:
Unknown task: foo. Pick one of: structuring, synthesis, vision, transcription, dream
Exits with code 1.
Validation
cd gnosys-public
npm run cli -- check --help
npx vitest run src/test/check-command-handler.test.ts
Related commands
gnosys doctor— broader system health check (stores, embeddings, archive).gnosys setup— configure providers and API keys.gnosys config show— inspect current task routing.
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 · 86 lines · 0 tokens per session scan A b925c4a6c329
check 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 501 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
transcribe
Transcribes video/audio from URLs (YouTube, X, mp3, mp4, wav) using Whisper AI.
motion
Runtime entry point for configuring global motion tokens, scroll-reveals, and micro-delight interactions in motion.js and interactions.js.
tokens
Establish the single source of truth every other command reads from. This is the one command every later command depends on — re-running it (a rebrand, a palette fix) is how a change propagates to every page at once.
stop
Run this command to stop any currently playing TTS audio.
status
Check TTS playback status and configuration.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.