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/n-n-code/n-n-code-skills/project-core-devnpx skills add n-n-code/n-n-code-skills --skill project-core-devgit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWhat 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.00043 | $0.00313 |
| Opus 5 | $0.00022 | $0.00156 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
project-core-dev 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 2d 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
Project Core Dev
This is a thin project overlay, not a standalone implementation workflow. Use it with matching implementation guidance only when repository-specific checks or gaps remain unclear. Omit it when another selected skill plus repo context already supplies exact commands and reporting obligations.
When to use
The task is a routine repo-owned change whose completion path is not yet concrete.
Not for
Use project-config-and-tests, project-platform-diagnose,
project-release-maintainer, or project-vendor-boundary when that specialized
concern leads. Do not use this skill to restate a generic validation checklist.
Completion Workflow
- Read the applicable repository instructions, README, CI configuration, contributor docs, and presets. Identify authoritative commands and mandatory gates; do not invent a second workflow.
- Map the touched surface to the narrowest honest repo-defined proof. Do not run broad checks merely because they exist.
- Execute within the task's authority. Prefer check modes for read-only work; do not install tools, start services, or mutate the environment just to close a checklist.
- Report exact commands, outcomes, gaps, and the narrowest next command that would close each material gap without implying it passed.
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.
- 2d ago First seen · 36 lines · 43 tokens per session scan A 55870902dbbb
project-core-dev is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 313 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-31.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
laundering
Use when all territories report completion after the hit — handles integration, verification, consigliere final review, cleanup, and ledger updates to produce clean production-ready code.
reconnaissance
Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review.
the-grilling
Use when adversarial brainstorming is needed after reconnaissance — the Proposer, Devils-Advocate, and Synthesizer each run ONE pass (no rounds); the Don is grilled on the IDEA first, one question at a time, then the proposal is attacked.
using-gangsta
Use when starting any conversation — establishes how to find and use Gangsta skills, enforces the 1% invocation rule, maps platform tools, and routes the Don's intent through the Gangsta Agents Family hierarchy.
drill-tdd
Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first.