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/tggo/templui-mcp-server/update-componentsgit clone --depth 1 https://github.com/tggo/templui-mcp-serverWrote 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/tggo/templui-mcp-server/update-components)<a href="https://agentmods.dev/commands/tggo/templui-mcp-server/update-components"><img src="https://agentmods.dev/badge/commands/tggo/templui-mcp-server/update-components.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.01135 |
| Opus 5 | $0.00000 | $0.00567 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
update-components 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update TemplUI Components
Automatically update the MCP server to support the latest TemplUI components from the repository.
What this command does:
- Discovery: Fetches the current component list from TemplUI GitHub repository
- Analysis: Compares repository components with the current static list
- Metadata Collection: Retrieves component information from templui.io documentation
- Update: Updates all necessary files with new/removed components
- Validation: Builds and tests to ensure nothing breaks
- Version Bump: Increments version number appropriately
- Documentation: Updates README, CHANGELOG, and creates update summary
- Deployment: Commits, tags, pushes to GitHub, and publishes to npm
Steps to execute:
Phase 1: Discovery & Analysis
- Build the project to ensure clean state
- Run dynamic component discovery from GitHub API
- Compare with current static component list (src/data/components-list.ts)
- Identify new components that need to be added
- Identify deprecated components that need to be removed
- For each new component, check if it has JavaScript file
- Fetch documentation from templui.io to determine:
- Component category (form/layout/navigation/overlay/feedback/display)
- Component description
- Features and capabilities
Phase 2: Update Files
Update the following files:
1. src/data/components-list.ts
- Add new component entries with proper metadata
- Remove deprecated component entries
- Maintain alphabetical order within the array
2. src/utils/updater.ts
- Update the
componentNamesarray ininvalidateComponentCache()method - Add new component names to cache invalidation list
- Remove deprecated component names
3. README.md
- Update "Supported Components" section with new count
- Update component lists by category
- Update any examples that reference deprecated components
4. CLAUDE.md
- Update "Supported Components" section with new count
- Update category lists
- Update JavaScript-enabled components list
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 · 146 lines · 0 tokens per session scan A 6c5cb78e78cc
update-components is a command published in the GitHub repository tggo/templui-mcp-server (1 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,135 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.