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/minghinmatthewlam/agent-guards/uithubgit clone --depth 1 https://github.com/minghinmatthewlam/agent-guardsWhat 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.00484 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
uithub scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Determine the repository’s default branch (e.g., `curl -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/<owner>/<repo> | jq -r '.default_branch'`). If discovery fails, fall back to `main` but m What it actually says
Purpose: fetch UiThub repo context for a GitHub project without cloning.
Inputs
$REPO_URL(required): GitHub URL orowner/reposlug.$CONTEXT(optional): focus areas/questions to guide which files to fetch.
Flow
- Validate
$REPO_URL. If missing or invalid, ask the user for a correct value. - Normalize to
<owner>/<repo>and extract any path hints from$REPO_URL. - Determine the repository’s default branch (e.g.,
curl -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/<owner>/<repo> | jq -r '.default_branch'). If discovery fails, fall back tomainbut mention the assumption. - Fetch structure only:
curl "https://uithub.com/<owner>/<repo>?accept=text/plain&omitFiles=true" > tree.txt - Pull key docs (adjust lines) using the discovered branch:
curl "https://uithub.com/<owner>/<repo>/tree/$BRANCH/README.md?accept=text/plain&plain=1&lines=200" > readme.txt- Fetch other docs (
CONTRIBUTING.md,docs/overview.md, etc.) when$CONTEXTsuggests. - After each
curl, check the output (status code, byte size). Retry withplain=1,?path=..., orhttps://raw.githubusercontent.com/<owner>/<repo>/$BRANCH/...if the response is empty or a 404.
- Fetch other docs (
- Capture code slices guided by
$CONTEXT:- Start with
curl "https://uithub.com/<owner>/<repo>/tree/$BRANCH/<path>?accept=text/plain&plain=1&lines=200"for targeted files. - For larger sections, use
curl "https://uithub.com/<owner>/<repo>?accept=text/plain&path=<path>", then trim locally. - If UiThub still returns nothing, fall back to
https://raw.githubusercontent.com/<owner>/<repo>/$BRANCH/<path>.
- Start with
- Summarize what each artifact reveals and note gaps needing further UiThub pulls or a full clone, explicitly tying the findings back to
$CONTEXT.
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 · 0 tokens per session scan A 2690445743bb
uithub is a command published in the GitHub repository minghinmatthewlam/agent-guards (36 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.