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 skilld-dev/skilld --skill generate-project-skillgit clone --depth 1 https://github.com/skilld-dev/skilldWrote 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/skilld-dev/skilld/generate-project-skill)<a href="https://agentmods.dev/skills/skilld-dev/skilld/generate-project-skill"><img src="https://agentmods.dev/badge/skills/skilld-dev/skilld/generate-project-skill/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/skilld-dev/skilld/generate-project-skill"><img src="https://agentmods.dev/badge/skills/skilld-dev/skilld/generate-project-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.01064 |
| Opus 5.5 | $0.00010 | $0.00426 |
| Sonnet 5.5 | $0.00005 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
generate-project-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a project Skill
Create a compact, searchable Skill from the project itself. This Skill is for maintainers who author a draft Skill they own.
Inputs
Use the project directory or prepared project source. Ask for the destination only when the request does not provide one.
Inspect
- Read project instructions and decision records first.
- Read manifests, exported entry points, and build configuration.
- Find the test, lint, typecheck, build, and release commands.
- Trace the main public workflows through their real entry points.
- Note generated directories and files an Agent must not edit.
- Check recent changes when they explain current conventions.
Project navigation
The Skill must let an Agent find any part of the project without a prior index.
- Name the project from its manifest. Use the directory name when no manifest names it.
- List the entry points the manifest declares, such as
main,module,types,exports, andbin. - List the source and documentation directories an Agent reads most.
- Use project-relative paths for every file pointer.
- Never add a generated directory prefix to a project-relative path.
- Give search commands the Agent can repeat, scoped to those directories.
- Prefer
rgfor search. Name the directories to skip in the command. - Tell the Agent when project changes require a new Skill run.
Write the search commands so their results point at real project files.
Skip these paths while collecting project files:
- version-control data, such as
.git - dependency directories, such as
node_modulesandvendor - generated output, such as
dist,build,target,.output,.nuxt, and.next - caches and reports, such as
coverage - credential files, such as
.envand any private key
Skip any file larger than 512 KB. Do not follow symbolic links while collecting project files.
Output
Write one directory whose name matches the Skill name.
The directory must contain SKILL.md.
Use references/ for architecture details and command guides.
Use scripts/ only for reusable automation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago Changed · +6 lines c1c69c264c15
- 14d ago Changed · +20 lines 0547f12f2b6d
- 20d ago Changed · +1 lines 2c8faa9ba29f
- 27d ago Changed · +14 lines af2894a15257
- 1mo ago Changed · +1 lines 9c3ca80b0ece
- 1mo ago First seen · 63 lines · 25 tokens per session scan A 48306372ac9b
generate-project-skill is a skill published in the GitHub repository skilld-dev/skilld (327 stars, last pushed 10d ago), licensed MIT. It adds 25 tokens to every session and 1,064 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-30.
Other skills, from other repositories
use-agent-supagents
Compile shared role instructions into native subagent profiles for Antigravity, Claude Code, Codex, Copilot, Cursor, Gemini CLI, Grok, Kilo, and OpenCode.
harness-config-cli
Use when working in the harness-config repository and Codex needs to validate, preview, activate, or explain Harness config dogfooding with the local @harnessconfig/cli package.
harness-config-patterns
Use when working in the harness-config repository on implementation structure, projection architecture, resource and dir composition, target override precedence, profile and ignore integration, or code placement.
harness-config-specs
Use when working in the harness-config repository on the Harness config v1 standard, conformance rules, specification wording, manifest/resource/dir/profile/ignore semantics, or docs ownership.
harness-config-testing
Use when working in the harness-config repository on test strategy, regression coverage, fixtures, docs/TESTING.md, CLI end-to-end checks, projection edge cases, profile and ignore scenarios, or focused quality commands.
.claude
Review changes for correctness, tests, and generated-output drift. When Claude specific behavior is relevant, call out the generated .claude surface.