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/fsearchgit 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.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
fsearch 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 fsearch
Federated search across project, user, and global scopes with tier boosting.
Usage
gnosys fsearch "auth tokens"
gnosys fsearch "auth tokens" --scope project,user
gnosys fsearch "auth tokens" --no-global --json
gnosys fsearch "auth tokens" --directory /path/to/project --limit 10
Options
| Option | Description |
|---|---|
-l, --limit <n> |
Max results (default 20) |
-d, --directory <dir> |
Project directory for context detection |
--no-global |
Exclude global-scope memories |
--scope <scope> |
Filter scopes: project, user, global (comma-separated) |
--json |
Output results as JSON |
Behavior
- Opens central DB; exits if unavailable (
Central DB not available.). - Detects current project via
--directorywhen provided. - Parses comma-separated
--scopevalues. - Calls
federatedSearchwithincludeGlobalderived from Commander's--no-globalnegation (opts.global). - Closes central DB in
finally.
Human output
Prints project context line, then ranked results with scope, score, boosts, and snippet preview.
No results:
No results for "<query>".
Context lines:
Context: project <projectId>
or
No project detected
JSON output
{
"query": "...",
"projectId": "...",
"count": 3,
"results": [ ... ]
}
Validation
cd gnosys-public
npm run cli -- fsearch --help
Related commands
gnosys search— local FTS search without federated tier boosting.gnosys discover— keyword discovery.
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 · 76 lines · 0 tokens per session scan A f7f3ce548f4d
fsearch 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 430 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.