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 meganemura/headsign --skill create-project-skillgit clone --depth 1 https://github.com/meganemura/headsignWrote 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/meganemura/headsign/create-project-skill)<a href="https://agentmods.dev/skills/meganemura/headsign/create-project-skill"><img src="https://agentmods.dev/badge/skills/meganemura/headsign/create-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/meganemura/headsign/create-project-skill"><img src="https://agentmods.dev/badge/skills/meganemura/headsign/create-project-skill.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.00047 | $0.00381 |
| Opus 5.5 | $0.00019 | $0.00152 |
| Sonnet 5.5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
create-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 29d 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
Create a project-local skill
Give the working agent the objective, constraints, available gates, and authority to choose its method. Derive completion from the user's request and repository contracts. CI, independent review, commits, or publication belong in completion only when those contracts require them.
Read references/procedure.md before authoring. Inspect the repository and preserve the provenance of its commands and requirements. Explain material gaps before treating the skill as usable. Preserve supplied command strings and their meaning. Discover missing checks when the request permits it; a copy-only request does not authorize additions. Do not impose a phase graph or create queue or ownership infrastructure.
The generated skill must require method assessment when meaningful feedback exposes a weakness, and at completion. The agent chooses a useful repair or justified retention within task authority and remaining budget. It applies repairs to the current work, verifies affected results, and preserves useful lessons. Explicit stops and required approvals continue to govern the work.
Write to .agents/skills/<name>/SKILL.md, unless the user or repository names
another contributor-skill location. Check that location's ignore and package rules.
Keep the skill usable with the project's own tools;
it must not depend on this authoring skill after generation.
Finish when the file expresses the contract, required commands are verified appropriately, and unresolved gaps are reported. Report what was checked. If the user also requested a trial, continue that authorized trial and use its observations to revise the skill.
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.
- 29d ago First seen · 39 lines · 47 tokens per session scan A 173816217004
create-project-skill is a skill published in the GitHub repository meganemura/headsign (1 stars, last pushed 28d ago), licensed MIT. It adds 47 tokens to every session and 381 once invoked, about $0.0002 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-10-01.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
context-exclusion
Maintain .agent-no-read.md markers for approved generated directories using deterministic scripts. Use when configuring generated-code context exclusion or restoring markers after regeneration, not for ordinary ignore rules or OS permissions.
context-lifecycle
Author, review, or integrate Agent Context Lifecycle Protocol V1 declarations and adapters. Use for explicit ephemeral messages, persistent named blocks, trusted discard controls, or agent compatibility questions; do not claim Codex itself can rewrite prior request history.
creating-workflows
A guide for creating reusable JavaScript workflows that coordinate several helper agents through steps, loops, parallel tasks, and summaries.
subagent-driven-development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
openspec
A specification-driven development process that records proposed software changes, implementation tasks, and updates to the project’s current behavior specifications.