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/royzhao1991/lingshu/helpnpx skills add RoyZhao1991/LingShu --skill helpgit clone --depth 1 https://github.com/RoyZhao1991/LingShuWhat 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.00053 | $0.00650 |
| Opus 5 | $0.00026 | $0.00325 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
help 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- help — 100% identical, 0 lines differ
What it actually says
Grok Help
Answer the user's question about Grok setup, configuration, or features.
Steps
-
If the question is about current config (what MCP servers, models, or settings are active), read
~/.grok/config.toml. MCP servers are under[mcp_servers.*]sections. -
If the question is about how to do something (setup, adding MCP servers, creating skills, authentication, keyboard shortcuts, troubleshooting), first check the user-guide docs at
~/.grok/docs/user-guide/. The available guides are:01-getting-started.md-- Installation, first launch, basic interaction02-authentication.md-- Browser login, API keys, OIDC, external auth03-keyboard-shortcuts.md-- Complete key bindings reference04-slash-commands.md-- All / commands05-configuration.md-- config.toml, pager.toml, env vars06-theming.md-- Themes, appearance customization07-mcp-servers.md-- MCP server setup and management08-skills.md-- Creating and using skills09-plugins.md-- Plugin marketplace10-hooks.md-- Lifecycle hooks11-custom-models.md-- BYOK, Ollama, OpenAI endpoints12-project-rules.md-- AGENTS.md project rules13-memory.md-- Cross-session memory14-headless-mode.md-- CLI scripting and CI/CD15-agent-mode.md-- ACP/stdio IDE integration16-subagents.md-- Subagents and personas17-sessions.md-- Session management18-sandbox.md-- Sandbox mode19-plan-mode.md-- Plan mode20-background-tasks.md-- Background tasks and monitoring21-terminal-support.md-- tmux, SSH, truecolor, clipboard, /terminal-setup Read the relevant guide(s) for the user's question. If none match, fall back to~/.grok/README.mdfor the comprehensive reference.
-
To modify config for the user, edit
~/.grok/config.tomlwith search_replace. -
To create a skill for the user, create
~/.grok/skills/<name>/SKILL.md(read~/.grok/docs/user-guide/08-skills.mdfor the SKILL.md format).
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 · 51 lines · 53 tokens per session scan A 4595c5fc67cb
help is a skill published in the GitHub repository RoyZhao1991/LingShu (11 stars, last pushed 13d ago), licensed Apache-2.0. It adds 53 tokens to every session and 650 once invoked, about $0.0003 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
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
docs-audit
Assess a published or in-progress documentation page for quality, accuracy, and voice compliance. Use before rewriting a page, during periodic health checks, when community signals point to confusion, or when comparing against competitor docs. Also triggers on "audit this page", "assess the docs", "what's wrong with…
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
pr-create
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.