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/ashermahonin/agentic-skills/init-projectnpx skills add ashermahonin/agentic-skills --skill init-projectgit clone --depth 1 https://github.com/ashermahonin/agentic-skillsWrote 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/ashermahonin/agentic-skills/init-project)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/init-project"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/init-project.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.1 | $0.00070 | $0.00700 |
| Opus 5 | $0.00035 | $0.00350 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
init-project 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Project
Purpose
Establish the project context before implementation. Inspect an existing repository, scaffold an empty one from an agreed intent, or combine both for a migration. Finish with a technical profile, project memory, and the next route.
Inputs
- Read
references/init-decision-tree.md. - Inspect the directory shape and probe the stack markers listed in the reference. Avoid reading the whole repository before the likely entrypoints are known.
- Choose fingerprint, scaffold, or hybrid mode.
- If the user passed a free-text intent, route to
intake-coordinatorfor a 30-second clarification before scaffolding.
Decision process
- Build the technical fingerprint: languages, frameworks, platforms, package manager, test and build commands, deployment target, CI, secret handling, observability, and canonical documentation entrypoint.
- In scaffold mode, compare viable stacks against the confirmed intent. Verify current framework and platform behavior before selecting one.
- In hybrid mode, map the existing boundaries before proposing the new slice or migration.
- Preserve existing
AGENTS.md,CLAUDE.md,GEMINI.md,.agents/,.claude/,.codex/,.gemini/, and.github/configuration. Propose a merge when an overlay is needed; never replace it silently. - Seed project memory only when the package skeleton is available and the chosen destination does not conflict with an existing vault. Otherwise provide the minimal note set to create.
- Record the mode, fingerprint, unknowns, next route, and the first command or prompt that continues the work.
Decision boundaries
- Use Context7 MCP whenever the detected or proposed stack involves an external library, framework, platform, API, or CLI whose current behavior shapes the scaffold.
- Keep stack choices and rejected alternatives tied to the project's actual constraints.
- Never overwrite an existing agent instruction file, client directory, or project vault.
- Do not scaffold when product intent, target platform, or data boundary is still materially ambiguous.
What ships with it
2 files 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.
- 5d ago First seen · 59 lines · 70 tokens per session scan A 4db486a707a0
init-project is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 12d ago), licensed MIT. It adds 70 tokens to every session and 700 once invoked, about $0.0003 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.