Skill Seekers converts documentation, code repositories, PDFs, videos, notebooks, and other sources into structured knowledge assets for AI skills, retrieval systems, and coding assistants. Developers use it to prepare source material for tools such as Claude, Gemini, OpenAI, LangChain, LlamaIndex, Cursor, Windsurf, and Cline, with exports for multiple targets. The catalogue entries provide skills, commands, instructions, an MCP integration, and a plugin for using the project.
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/yusufkaraaslan/skill_seekers/wordnpx skills add yusufkaraaslan/Skill_Seekers --skill wordgit clone --depth 1 https://github.com/yusufkaraaslan/Skill_SeekersWrote 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/yusufkaraaslan/skill_seekers/word)<a href="https://agentmods.dev/skills/yusufkaraaslan/skill_seekers/word"><img src="https://agentmods.dev/badge/skills/yusufkaraaslan/skill_seekers/word.svg" alt="Measured on agentmods" height="20"></a>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.00011 | $0.00803 |
| Opus 5 | $0.00005 | $0.00402 |
| Sonnet 5 | $0.00002 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
golden-word 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 6d 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
89% identical to golden-html-multi — 37 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golden_Word Documentation Skill
Use when testing the word golden build
📋 Document Information
Title: The Manual
Author: John Roe
Created: 2023-05-05
Modified: 2024-02-02
💡 When to Use This Skill
Use this skill when you need to:
- Understand golden_word concepts and fundamentals
- Look up API references and technical specifications
- Find code examples and implementation patterns
- Review tutorials, guides, and best practices
- Explore the complete documentation structure
📖 Section Overview
Total Sections: 3
Content Breakdown:
- manual: 3 sections
🔑 Key Concepts
Main topics covered in this documentation
Major Topics:
- Getting Started Guide
- Troubleshooting
Subtopics:
- Installation Steps
- API Usage
- Common Errors
⚡ Quick Reference
Common documentation patterns found:
Getting Started (1 sections):
- Getting Started Guide (section 1)
Troubleshooting (1 sections):
- Troubleshooting (section 3)
Usage (1 sections):
- API Usage (section 2)
📝 Code Examples
High-quality examples extracted from documentation
Bash Examples (1)
Example 1 (Quality: 6.0/10):
pip install thing
Python Examples (2)
Example 1 (Quality: 9.5/10):
def long_example():
x0 = 0
x1 = 1
x2 = 2
x3 = 3
x4 = 4
x5 = 5
x6 = 6
x7 = 7
x8 = 8
x9 = 9
x10 = 10
x11 = 11
x12 = 12
x13 = 13
x14 = 14
x15 = 15
x16 = 16
x17 = 17
x18 = 18
x19 = 19
x20 = 20
x21 = 21
x22 = 22
x23 = 23
x24 = 24
x25 = 25
x26 = 26
x27 = 27
x28 = 28
x29 = 29
x30 = 30
x31 = 31
x32 = 32
x33 = 33
x34 = 34
x35 = 35
x36 = 36
x37 = 37
x3
...
Example 2 (Quality: 8.5/10):
print('hello')
📊 Table Summary
2 table(s) found in document
From section: Getting Started Guide
| Option | Default |
|---|---|
| debug | false |
| port | 8080 |
What ships with it
3 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.
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.
- 6d ago First seen · 168 lines · 11 tokens per session scan A 2ace83e555fb
golden-word is a skill published in the GitHub repository yusufkaraaslan/Skill_Seekers (14,911 stars, last pushed 6d ago), licensed MIT. It adds 11 tokens to every session and 803 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to golden-html-multi, differing in 37 lines, and is treated as a copy.
Other skills, from other repositories
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
grill-me
Two modes, picked from the file you point it at. Contract mode grills a claude-contract.md line by line until every line is a thing Claude must always do or must never do, editing that file in place and creating nothing new. Brief mode interrogates a design brief until it has no soft spots left, then produces a…
information-architecture
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.
design-tokens
Establish color, typography, spacing, radius and motion as named role-based tokens. Use before building any interface.
heuristic-evaluation
Audit a design against Nielsen's ten usability heuristics, tying every finding to a specific element with a specific fix. Use on a built screen or a detailed mockup.
persona-acid-test
Stress-test a design through three lenses, confused user, skeptical engineer and impatient PM, before it goes to a stakeholder. Requires an actual design, an HTML file, Figma link or screenshot.