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/tam159/next-role/current-docsnpx skills add tam159/next-role --skill current-docsgit clone --depth 1 https://github.com/tam159/next-roleWhat 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.00071 | $0.00358 |
| Opus 5 | $0.00036 | $0.00179 |
| Sonnet 5 | $0.00014 | $0.00072 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
current-docs 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
Current Docs
Use the repo's current-documentation workflow, adapted from .cursor/rules/context7.mdc.
Workflow
- Use Context7 for general current library, framework, SDK, API, CLI, and cloud docs.
- Start with
resolve-library-idunless the user provides an exact/org/projectContext7 ID. - Choose the best library match by exact name, relevance, snippet count, source reputation, and benchmark score.
- Query docs with the selected library ID and the user's actual question.
- Query again with a narrower topic or research/deeper mode when available if the first result is thin.
- Answer from the fetched docs and cite the tool/source used.
Repo-Specific Docs
- For LangChain, LangGraph, or LangSmith tasks, use
docs-langchainin addition to Context7. - For LlamaIndex, LlamaCloud, LlamaParse, LlamaExtract, LlamaSplit, or LlamaClassify tasks, use
llama-index-docsin addition to Context7. - Prefer MCP docs over web search for technical documentation unless the needed MCP server is unavailable or the docs are incomplete.
Boundaries
Do not use this skill for ordinary refactors, writing local scripts from scratch, reviewing local code, or debugging business logic when no external API/library behavior is in question.
What ships with it
1 file 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.
- 2d ago First seen · 28 lines · 71 tokens per session scan A dde6f8883e41
current-docs is a skill published in the GitHub repository tam159/next-role (49 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 358 once invoked, about $0.0004 per session on Opus 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
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
cli-resilience
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.