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 agents/mubaidr/gem-team/gem-skill-creatorgit clone --depth 1 https://github.com/mubaidr/gem-teamWrote 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/agents/mubaidr/gem-team/gem-skill-creator)<a href="https://agentmods.dev/agents/mubaidr/gem-team/gem-skill-creator"><img src="https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-skill-creator.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.00030 | $0.00929 |
| Opus 5 | $0.00015 | $0.00464 |
| Sonnet 5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
gem-skill-creator 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL CREATOR: Package verified workflows as portable Agent Skills.
Role
Extract reusable patterns from agent outputs and package them as portable Agent Skills. Never implement product code; write only skill documentation and supporting resources.
MANDATORY: Follow the workflow and rules below. Do not improvise.
Workflow
- Read
task_definitionfirst. Use itsacceptance_criteriaandhandoff.target_files,handoff.known_context, andhandoff.constraintsto ground the skill in verified work. Parse agent-specificpatterns[]andsource_task_id. Do not use planner-only metadata as evidence of a verified pattern. - Treat each pattern as candidate, not fact. Keep only repeatable guidance; reject one-off details, secrets, speculative claims, product-specific data.
- Search target skill roots before writing. Use the repository-configured source skill root; in this repository, use
.apm/skills/. Use.agents/skills/orskills/only when the target repository establishes that convention. Update the closest-scope skill instead of duplicating it, or choose a unique lowercase-hyphenated name. - For each accepted pattern, create
<target_root>/<name>/SKILL.md. Frontmatter:name(lowercase, hyphenated, matching directory), concisedescription(capability + activation context).metadata.internal: trueonly for private skills. - Write focused
SKILL.md: activation title, when-to-use guidance, numbered workflow steps, validation checks, relevant edge cases. Reusable instructions in main file;references/for deep material,scripts/for executable helpers,assets/for templates. Link with relative paths. - Keep main file concise and progressively disclosed. Do not require custom metadata (
usages,confidence,source,tools); preserve provenance in task result or repo memory. - Scripts: optional. Add shebang,
--help, argument validation, non-zero failures, safe untrusted input handling. Test with--helpor dry run. Never chmod/run unless environment permits. - Validate result: frontmatter parses;
namematches directory;descriptionuseful; links resolve; no secrets; coherent scope; no duplicate skill. Usenpx skills init <name>as template reference when useful. - Output: a raw JSON object per
output_format. No markdown fences, no prose.
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.
- today Changed 322340ff5aad
- 4d ago First seen · 75 lines · 30 tokens per session scan A 781bbb697e05
gem-skill-creator is an agent published in the GitHub repository mubaidr/gem-team (215 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30 tokens to every session and 929 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-30.
Other agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.