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 skills/shyamsridhar123/agentsmith-cli/github-url-normalization-and-clonenpx skills add shyamsridhar123/agentsmith-cli --skill github-url-normalization-and-clonegit clone --depth 1 https://github.com/shyamsridhar123/agentsmith-cliWrote 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/skills/shyamsridhar123/agentsmith-cli/github-url-normalization-and-clone)<a href="https://agentmods.dev/skills/shyamsridhar123/agentsmith-cli/github-url-normalization-and-clone"><img src="https://agentmods.dev/badge/skills/shyamsridhar123/agentsmith-cli/github-url-normalization-and-clone.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.00023 | $0.00182 |
| Opus 5 | $0.00012 | $0.00091 |
| Sonnet 5 | $0.00005 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
github-url-normalization-and-clone 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
Github Url Normalization And Clone
Normalize GitHub URLs and perform shallow clones to a temp directory with cleanup.
When to Use
Use this skill when:
- Working with code in
src/utils/git.ts/ - User mentions "git"
- User mentions "clone"
- User mentions "github url"
- User mentions "normalize"
- User mentions "shallow"
Patterns
- GitHub URL detection and normalization
- temp dir naming with random suffix
- shallow clone with --depth 1
- cleanup via fs.rm on completion
Examples
const { path, cleanup } = await cloneRepo(url); await cleanup();
Category
reliability - Error handling, recovery, and fault tolerance
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 · 37 lines · 23 tokens per session scan A 7d9d8502a145
github-url-normalization-and-clone is a skill published in the GitHub repository shyamsridhar123/agentsmith-cli (16 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 182 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-30.
Other skills, from other repositories
oda-copilot-customization
Apply, review, improve, or maintain a repository's Copilot customization with the Ownership-Driven AI Customization Architecture and the latest official GitHub Copilot docs. Use when shaping or auditing a repository's customization map, governance files, supporting docs, and safeguards for drift, health, weak…
oda-task-tracking
Operate ODA GitHub Issues and the ODA Board consistently. Use when creating, updating, listing, moving, or reclassifying tracked work in GitHub for this repository.
impact-review
Assess likely downstream impact, decide what should be reconciled now versus carried forward explicitly, and keep the repository coherent without sweeping every related surface.
debug-behavior
Investigate inconsistent or incorrect behavior with a structured workflow.
error-recovery
Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure.
security-review
How to review PRs for security — credentials, injection, workflow permissions, supply chain, git operation safety.