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/tonykipkemboi/skill-foundry/example-skillnpx skills add tonykipkemboi/skill-foundry --skill example-skillgit clone --depth 1 https://github.com/tonykipkemboi/skill-foundryWrote 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/tonykipkemboi/skill-foundry/example-skill)<a href="https://agentmods.dev/skills/tonykipkemboi/skill-foundry/example-skill"><img src="https://agentmods.dev/badge/skills/tonykipkemboi/skill-foundry/example-skill.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.00037 | $0.00470 |
| Opus 5 | $0.00018 | $0.00235 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
example-skill 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.
What it actually says
Example Skill Title
REPLACE: Brief intro explaining what this skill does and what the user gets from it.
Configuration: List any required MCP connections or tool integrations here, e.g. "This skill requires the calendar MCP connector. See
shared-tool-reference.mdfor setup."
Quick Reference
- Sources: List data sources (e.g. Google Calendar, Gmail, Slack)
- Output: Describe what the skill produces
Pre-flight Connection Check (if the skill depends on an external tool)
Always run first. Verify connections before doing real work:
{
"toolkits": ["googlecalendar", "gmail"],
"session_id": "example-skill"
}
| Result | Action |
|---|---|
| All connections Active | Proceed to Step 1 |
| Required tool/MCP not available | Stop. Tell the user which connector to enable and where. |
| Any connection not active | Show auth URL. Retry once. If still failing, stop and report. |
Workflow
Step 1: [First Step Name]
REPLACE: Describe what Claude should do in this step. Be specific, since Claude follows instructions literally. If the user passed an argument, it is available as $ARGUMENTS (matching the argument-hint in the frontmatter); use it here or remove the hint if the skill takes no argument.
Step 2: [Second Step Name]
REPLACE: Continue with subsequent steps.
Step 3: Present Output
## [Output Title]
### [Section 1]
[Content]
### [Section 2]
[Content]
Guidelines
- REPLACE with rules specific to this skill
- Keep responses scannable: use headers and bullet points
- Parallelize tool calls wherever possible
- Always confirm intent before taking actions (sending messages, creating events)
- No speculation; only include information from actual data sources
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 · 70 lines · 37 tokens per session scan A 6d82344362df
example-skill is a skill published in the GitHub repository tonykipkemboi/skill-foundry (2 stars, last pushed 18d ago), licensed MIT. It adds 37 tokens to every session and 470 once invoked, about $0.0002 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…