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 chenfei462/packsmith --skill github-demandgit clone --depth 1 https://github.com/chenfei462/packsmithWrote 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/chenfei462/packsmith/github-demand)<a href="https://agentmods.dev/skills/chenfei462/packsmith/github-demand"><img src="https://agentmods.dev/badge/skills/chenfei462/packsmith/github-demand/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/chenfei462/packsmith/github-demand"><img src="https://agentmods.dev/badge/skills/chenfei462/packsmith/github-demand.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.00022 | $0.00175 |
| Opus 5.5 | $0.00009 | $0.00070 |
| Sonnet 5.5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
github-demand 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 2mo 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 Demand
Use this skill when a project idea needs evidence from GitHub rather than intuition.
Workflow
- Start from trending repos and topic pages.
- Look for repositories with strong star velocity or fast issue growth.
- Read open issues to identify repeated workflow pain.
- Separate category proof from unsolved workflow gaps.
- End with one narrow product recommendation, not a vague market map.
Output
- one-sentence thesis
- 3-5 demand signals
- 2-3 user pains
- one MVP recommendation
Rules
- Prefer primary GitHub sources.
- Include exact dates when calling something "latest" or "recent".
- Distinguish evidence from inference.
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.
- 2mo ago First seen · 30 lines · 22 tokens per session scan A 1e56553286a0
github-demand is a skill published in the GitHub repository chenfei462/packsmith (2 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 175 once invoked, about $0.0001 per session on Opus 5.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
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
promptkitty-assemble
Discover and assemble a task-specific prompt from the embedded PromptKit catalog through the PromptKitty CLI. Use when the user wants to select a PromptKit template, compose a prompt for an engineering task, run an interactive PromptKit intake, write a requirements or design artifact, investigate a bug, review code…
promptkitty-author-agent-instructions
Turn a fully assembled PromptKit prompt into ready-to-commit project instructions or a provider-native subagent profile. Use when the user asks to create persistent agent guidance, custom agent instructions, an agent profile, a subagent, or equivalent files for Codex, Claude Code, Grok Build, GitHub Copilot, OpenCode…
prompt-improver
Transform vague prompts into precise, verifiable structured XML prompts that coding agents execute reliably. Modes: execute (default — generate then run) and plan (generate XML for review first). Use when the user says improve prompt, make this work better, prompt engineer, structure a request, plan a complex change…
prompt-improver
Turn a vague coding request into a precise, verifiable XML spec, then execute it or show it for review. Use when the user asks to improve a prompt, structure a request, or plan a complex change before coding. Skip it when the request is already a detailed spec. Served by the prompt-improver MCP server.
code-reviewer
A code-review workflow written in Chinese that checks software changes for correctness, security, performance, and maintainability. It also defines a report format for critical issues and suggestions.