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 commands/jsk9999/ai-nexus/update-docsgit clone --depth 1 https://github.com/JSK9999/ai-nexusWrote 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/commands/jsk9999/ai-nexus/update-docs)<a href="https://agentmods.dev/commands/jsk9999/ai-nexus/update-docs"><img src="https://agentmods.dev/badge/commands/jsk9999/ai-nexus/update-docs.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 | $0.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
update-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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Project Documentation
You are tasked with updating /docs/README.md to reflect the current state of the project.
Your Responsibilities
-
Analyze Current Project Structure
- Note any new directories or significant changes
- read package.json
- read .env.example
-
Review Recent Changes
- Check git status for uncommitted changes
- Review recent commits (last 5-10) using
git log --oneline -10 - Identify modified, added, or deleted files
- Use
git diff HEAD~5..HEAD --statto see what changed recently
-
Update Documentation
- Read the current
/docs/README.md - Update the project structure section if directories changed
- Add a "Recent Changes" section with:
- Date of last update
- Summary of recent modifications
- New features or components added
- Removed or deprecated items
- Keep the documentation concise and well-structured
- Read the current
-
Generate docs/RUNBOOK.md with:
- Deployment procedures
- Monitoring and alerts
- Common issues and fixes
- Rollback procedures
-
Identify obsolete documentation:
- Find docs not modified in 30+ days
- List for manual review
-
Documentation Format The README should follow this structure:
# Project Documentation > Last Updated: YYYY-MM-DD ## Overview Brief description of the project ## Project Structureconfig/ai/claude/ ├── agents/ # Custom AI agents ├── commands/ # Slash commands ├── contexts/ # Context definitions ├── hooks/ # Lifecycle hooks ├── ...
## Components ### Agents - Description of agents ### Commands - List of available commands ### Hooks - Installed hooks and their purposes [... other sections ...] ## Recent Changes ### YYYY-MM-DD - Added: ... - Modified: ... - Removed: ... -
Important Guidelines
- ALWAYS read the current README first before making changes
- Preserve existing content unless it's outdated
- Use clear, concise language
- Group related changes together
- Only update the "Recent Changes" section if there are actual changes
- DO NOT add placeholder or example content
- Write in Korean for descriptions, keep code/paths in English
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.
- 4d ago First seen · 95 lines · 0 tokens per session scan A e609a65a285c
update-docs is a command published in the GitHub repository JSK9999/ai-nexus (19 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 617 tokens. 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 commands, from other repositories
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
terse
Switch reply compression level — /terse [lite|full|ultra|off]. Complements RTK (input savings) with output-side savings.
promote
Promote project-scoped instincts to global scope.
projects
List known projects and their instinct statistics.
csm-workledger
Show the surviving work-ledger entries across sessions.