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/halidsaglam/saglitzdesign-mcp/refresh-knowledgegit clone --depth 1 https://github.com/HalidSaglam/saglitzdesign-mcpWrote 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/halidsaglam/saglitzdesign-mcp/refresh-knowledge)<a href="https://agentmods.dev/commands/halidsaglam/saglitzdesign-mcp/refresh-knowledge"><img src="https://agentmods.dev/badge/commands/halidsaglam/saglitzdesign-mcp/refresh-knowledge.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.00024 | $0.00464 |
| Opus 5 | $0.00012 | $0.00232 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
refresh-knowledge 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.
What it actually says
Refresh the SaglitzDesign knowledge base. Follow this procedure:
-
Find stale docs. Compute each doc's age from its
updated:frontmatter field (all docs live underknowledge/**/*.md). Staleness thresholds by category: seo/geo 120 days; design-language/marketing 240 days; pattern 300 days; component/ux/craft/process 365 days; book 730 days. (Same thresholds as the server'sknowledge_freshnesstool — you can also run the built server and call that tool.) If the user passed arguments (e.g. a category or doc id), refresh only those instead. -
Re-research each stale doc with parallel agents. For each stale doc, launch a general-purpose agent that:
- Reads the current doc.
- Uses WebSearch/WebFetch to verify every dated claim (thresholds, specs, version-specific guidance) against current official sources; for
patterndocs, re-runs the original Mobbin MCP searches (load tools via ToolSearch "select:mcp__mobbin__search_screens,mcp__mobbin__search_flows,mcp__mobbin__search_sections"). - Edits the doc in place: corrects outdated facts, adds significant new developments, keeps the existing frontmatter format, updates the
sourcesarray, and setsupdated:to today's date. - Reports back a one-paragraph changelog (what changed, what was verified-unchanged).
-
Refresh the visual example library if stale (>300 days): re-run the Mobbin collection prompts (see git history for the original agent prompts), replacing dead images in
knowledge/examples/. -
Verify. Run
npm run buildand start the server once to confirm all docs still parse (stderr reports the loaded doc count — it must not drop). Spot-check one updated doc via aget_design_docJSON-RPC call. -
Commit with a message summarizing the changelog per doc.
Do not rewrite docs wholesale — surgical updates only; the curated structure and prescriptive tone must survive.
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 · 22 lines · 24 tokens per session scan A 8c094d2355a0
refresh-knowledge is a command published in the GitHub repository HalidSaglam/saglitzdesign-mcp (3 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 464 once invoked, about $0.0001 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-31.
Other commands, from other repositories
handoff
Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package.
discover
Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
test-plan
Run the full usability study workflow — research questions, participant criteria, tasks, metrics, and facilitation guide.
tm-main
Comprehensive command structure for Task Master integration with Claude Code.
help
Command "help" from WYRE-AI/autotask-mcp, covering task master command help, quick navigation, command categories, natural language examples and getting started.
learn
Learn about Task Master capabilities through interactive exploration.