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/keep-starknet-strange/starknet-agentic/update-docsgit clone --depth 1 https://github.com/keep-starknet-strange/starknet-agenticWrote 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/keep-starknet-strange/starknet-agentic/update-docs)<a href="https://agentmods.dev/commands/keep-starknet-strange/starknet-agentic/update-docs"><img src="https://agentmods.dev/badge/commands/keep-starknet-strange/starknet-agentic/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.1 | $0.00000 | $0.01141 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Website Documentation
This command updates the website documentation to reflect all changes made to the starknet-agentic repository since the last documentation update.
Execution Steps
Step 1: Get the Baseline Commit
Read website/CLAUDE.md and extract the commit hash from the docs-last-updated field at the end of the file. This is your baseline commit - the last commit that was reviewed for documentation updates. All changes after this commit need to be analyzed.
Step 2: Analyze All Changes Since Baseline
Run the following to get all changes since the last docs update:
git log --oneline <baseline_commit>..HEAD
git diff --stat <baseline_commit>..HEAD
CRITICAL: Do NOT rely on commit messages or summaries. You MUST:
- Read the actual changed files to understand what changed
- Explore the codebase to understand the current state of interfaces, APIs, and functionality
- Compare against what the documentation currently says
Use the Task tool with subagent_type=Explore to thoroughly research:
- Changes to MCP server tools (packages/starknet-mcp-server/)
- Changes to Cairo contracts (contracts/erc8004-cairo/, contracts/agent-account/, contracts/huginn-registry/)
- Changes to skills (skills/)
- Changes to examples (examples/)
- Changes to packages (packages/)
- Any new features, interfaces, or breaking changes
Step 3: Identify Documentation Gaps
Compare your findings against the existing documentation in website/content/docs/.
Documentation pages are defined in website/app/data/docs.ts and content lives in website/content/docs/{category}/{slug}.mdx.
Categories:
getting-started/- Introduction, installation, quick-start, configurationguides/- Wallet management, MCP server, DeFi operations, agent identityskills/- Individual skill documentationcontracts/- ERC-8004 contract documentationapi-reference/- MCP tools, A2A protocol, SDK methods
Step 4: Update Existing Documentation
For each piece of documentation that needs updating:
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 · 145 lines · 0 tokens per session scan A bb3dfc1447e8
update-docs is a command published in the GitHub repository keep-starknet-strange/starknet-agentic (80 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,141 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
orchestrate
This tool coordinates Claude Code's actions. It does NOT write code or create content.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.