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 skills add Stijnman/grok-custom-skills --skill github-repo-scoutgit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/github-repo-scout)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/github-repo-scout"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/github-repo-scout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/github-repo-scout"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/github-repo-scout.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00547 |
| Opus 5 | $0.00025 | $0.00273 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
github-repo-scout 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 12d 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 Repo Scout
When to Use
- User says github.com or task matches this capability
- User says check this repo or task matches this capability
- User says scout repo or task matches this capability
- User says what is this project or task matches this capability
Workflow
- Parse owner/repo from URL; reject non-GitHub hosts unless user confirms.
- Fetch README and top-level tree via public API or git clone (read-only).
- Compare README claims vs actual committed files (note drift).
- Check if repo exists locally in workspace or common clone paths.
- Summarize: purpose, install steps, risks, suggested actions (clone, audit, review).
- Do not access private repos without authenticated user context.
Integrations
oss-repo-maintainerdefensive-mcp-auditskill-rubric-reviewer
Error Handling
| Failure | Response |
|---|---|
| 404/private repo | State access limitation; ask user to clone locally. |
| Rate limited | Backoff; use local clone if available. |
Gotchas
- Public repos only unless user has authenticated MCP/GitHub access.
Safety & Ethics (Publication-Ready)
This skill is designed for public distribution. Constraints:
- Read-only repository inspection.
- No harvesting of tokens, secrets, or private issue content.
- Do not auto-clone into system directories without user approval.
Prohibited actions
- No unauthorized access, malware, or harmful automation
- No silent exfiltration of data, credentials, or telemetry
- No destructive system changes without hitl-approver
- No publication of user PII or environment secrets in outputs
Example
Input: User request matching triggers above. Output: Structured result per workflow; local artifacts only unless user opts in.
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.
- 12d ago First seen · 67 lines · 50 tokens per session scan A 885cc4a99d69
github-repo-scout is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 547 once invoked, about $0.0003 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 skills, from other repositories
goal-meta-skill
A guide for turning an unclear or complex task into a reviewable /goal instruction for coding agents.
workflow-to-skill
Turn a goal and existing CLI, MCP, HTTP, API, or external workflow capabilities into one reviewable reusable Agent Skill. Use when the user asks to create or revise a workflow SKILL.md without a dedicated interface for invocation or result presentation. A webpage, UI, image, or report produced as workflow output does…
rss-digest
Collect RSS or Atom sources and produce a traceable intelligence digest through the configured Weft workflow.
workflow-docs-sync
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
workflow-to-skill-with-surface
Create or revise one reusable workflow Skill plus an optional harness-native Prompt Surface that maps a dedicated form, Page, button set, command UI, or result view to ordinary Skill messages and Harness results. Use only when the user explicitly requests a dedicated interface for invoking the Skill or presenting its…
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.