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 skills/gmickel/gno/skillnpx skills add gmickel/gno --skill skillgit clone --depth 1 https://github.com/gmickel/gnoWhat 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.00086 | $0.07561 |
| Opus 5 | $0.00043 | $0.03780 |
| Sonnet 5 | $0.00017 | $0.01512 |
| Haiku 4.5 | $0.00009 | $0.00756 |
Grade A, and why
gno 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 3d 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.
This is a copy
97% identical to gno — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 618 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GNO - Local Knowledge Engine
Fast local semantic search. Index once, search instantly. Local inference needs no API key; configured HTTP backends and explicit gno.sh publishing are separate network boundaries.
When to Use This Skill
- User asks to search files, documents, or notes
- User wants to find information in local folders
- User needs to index a directory for searching
- User mentions PDFs, markdown, Word docs, code to search
- User asks about knowledge base or RAG setup
- User wants semantic/vector search over their files
- User needs to set up MCP for document access
- User wants a web UI to browse/search documents
- User wants a deterministic, budgeted evidence bundle for an agent task
- User asks to get AI answers from their documents
- User wants to tag, categorize, or filter documents
- User asks about backlinks, wiki links, or related notes
- User wants to visualize document connections or see a knowledge graph
- User wants to export a note or collection for gno.sh publishing
Quick Start
gno setup ~/docs --name docs # Index + prove exact BM25; semantic continues
gno search "your query" # BM25 keyword search
gno setup is the default activation path. It is idempotent, returns only
after exact lexical proof, and runs directly without resident/Web/MCP
attachment. Use --no-semantic to start no worker and record skipped state.
Inside a repository with .gno/index.yml, setup inspects the optional profile
before mutation. Run gno profile diff, then
gno setup . --apply-profile to apply its portable collection/context/content
rules before setup proves retrieval. Missing/invalid profiles keep ordinary
setup usable; no profile is applied implicitly.
Use repeatable --connector with claude-code-skill,
claude-desktop-mcp, cursor-mcp, codex-skill, opencode-skill,
openclaw-skill, or hermes-skill. Connector skips/failures can return
completed_with_actions without invalidating lexical success. Skill targets
are installed but report target_runtime_unverifiable.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- cli-reference.md 31 KB
- examples.md 10 KB
- mcp-reference.md 6.3 KB
- README.md 4.9 KB
- recipes/brain-first-lookup.md 1.3 KB
- recipes/capture-and-file.md 2.4 KB
- recipes/citation-and-provenance.md 2.4 KB
- recipes/email-context.md 1.5 KB
- recipes/idea-capture.md 1.3 KB
- recipes/meeting-ingestion.md 1.4 KB
- recipes/source-summary.md 1.2 KB
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.
- 3d ago First seen · 618 lines · 86 tokens per session scan A 69fc20500723
gno is a skill published in the GitHub repository gmickel/gno (109 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 7,561 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to gno, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
esm
Comprehensive toolkit for protein language models including ESM3 (generative multimodal protein design across sequence, structure, and function) and ESM C (efficient protein embeddings and representations). Use this skill when working with protein sequences, structures, or function prediction; designing novel…
google-workspace-setup
One-time setup for gws: install, OAuth, scopes, auto-approve.
google-calendar
Google Calendar via gws: list events, create, accept, find free time.
gini-bug-report
File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.
google-docs
Google Docs via gws: read, append text, structured batch edits.
google-drive
Google Drive via gws: search, list, upload, download, share.