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 skills add jellydn/my-ai-tools --skill doc-searchgit clone --depth 1 https://github.com/jellydn/my-ai-toolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jellydn/my-ai-tools/doc-search)<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/doc-search"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/doc-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/doc-search"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/doc-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 146 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
What 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.1 | $0.00026 | $0.01270 |
| Opus 5.5 | $0.00010 | $0.00508 |
| Sonnet 5.5 | $0.00005 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
doc-search 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Search
When to Use
Use this skill when:
- Starting work on a feature that may have existing decisions or ADRs
- Need to understand project conventions or patterns
- Looking for past design discussions or trade-off analyses
- Want to find relevant wiki entries or knowledge base articles
- Need to understand how existing documentation is structured
- Planning to write documentation and want to match existing style
What It Does
Helps you find and navigate existing project documentation using available tools (grep, qmd, fff, ctx). Documentation is often scattered across multiple locations — this skill provides a systematic approach to find what you need.
Where Documentation Lives
This project stores documentation in several locations:
| Location | Content | Best For |
|---|---|---|
docs/ |
User-facing guides (quick-start, tutorials) | Getting started, feature guides |
ADRs via configs/adr/* |
Architecture Decision Records | Why decisions were made |
wiki/ |
LLM wiki — entities, concepts, log | Knowledge base, cross-references |
MEMORY.md |
Durable project learnings and gotchas | Known issues, conventions |
skills/*/SKILL.md |
Agent skill definitions | Tool capabilities |
configs/*.md |
Tool-specific documentation | Per-tool behavior |
AGENTS.md |
Agent instructions and guidelines | Development workflow |
| qmd knowledge base | Indexed project knowledge | Searchable, AI-powered retrieval |
How to Search
Step 1: Find Relevant Documents
Use fff to locate documentation files:
fff "*.md" docs/ # All documentation files
fff "*adr*" # Architecture Decision Records
fff "*auth*" docs/ # Auth-related documentation
fff "*wiki*" # Wiki entries
Use rg (ripgrep) to search documentation content:
rg "decision" docs/ # Find decisions in docs
rg "ADR-0" . --glob "*.md" # Find ADR references
rg "rate.limiting" --glob "*.md" # Find docs about rate limiting
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.
- 1mo ago First seen · 165 lines · 26 tokens per session scan A db2b25512955
doc-search is a skill published in the GitHub repository jellydn/my-ai-tools (124 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,270 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other skills, from other repositories
ask-first
A decision guide for handling unclear requests before taking action. It uses one focused question or probe when the requested goal, context, or boundaries are not clear.
insight-miner
A manually triggered writing guide that turns notes, debugging records, design summaries, code snippets, or rough drafts into Chinese technical blog posts. It first identifies and evaluates possible article topics before writing.
book-recommender
A Chinese-language book recommendation and analysis skill that evaluates what books are about, whether they are worth reading, and how to read them.
notes-to-blog
A manually triggered guide for turning technical notes and rough material into a Chinese programming blog post. It first extracts and evaluates the main transferable idea, then writes the article after the user confirms its direction.
wisdom-decoder
A guided explanation skill for ideas from Buddhism, philosophy, and psychology. It presents a chosen topic in everyday language and connects it to practical actions, sources, and perspectives from other fields.
teach-me
A five-step teaching workflow for introducing an unfamiliar topic and guiding the learner toward applying it. It moves from an example and explanation to supported practice and an independent task.