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 photostructure/coding-skills --skill project-setupgit clone --depth 1 https://github.com/photostructure/coding-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/photostructure/coding-skills/project-setup)<a href="https://agentmods.dev/skills/photostructure/coding-skills/project-setup"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/project-setup/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/photostructure/coding-skills/project-setup"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/project-setup.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.00170 | $0.03059 |
| Opus 5.5 | $0.00068 | $0.01224 |
| Sonnet 5.5 | $0.00034 | $0.00612 |
| Haiku 4.5 | $0.00017 | $0.00306 |
Grade A, and why
project-setup 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 1mo 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native C/C++ Project Setup & Hardening
Assess a cross-platform modern-C++ (C++17) project — especially a Node.js native addon built with node-gyp and node-addon-api — against a practical, evidence-based baseline for build hardening, analysis tooling, portability, and maintainable code. Report applicable preventive-control gaps even when no defect is currently proven, while clearly distinguishing hardening advice from actual bugs.
Use the OpenSSF Compiler Options Hardening Guide as the compiler/linker backbone, the C++ Core Guidelines for code conventions, CERT C/C++ and the sanitizer/tool docs for analysis, and official node-gyp / Node-API documentation for the addon toolchain. See ATTRIBUTION.md.
Boundary with resource review
Keep this skill separate from resource-review:
This skill (project-setup) |
The resource-review skill |
|---|---|
| Asks whether applicable controls meet a baseline | Asks whether a memory/resource defect exists |
| Reports evidence-backed best-practice gaps | Reports only proven defects |
| Uses Met / Gap / Not applicable / Needs verification | Uses Critical / High / Medium / Low |
| Prioritizes Essential / Recommended / Optional | Prioritizes impact and trigger reachability |
A missing stack protector or an unset sanitizer job is a hardening Gap, not a
vulnerability. If the assessment uncovers an actual defect (a real leak, use-after-free,
or race), list it separately under Escalate to resource review and recommend
the resource-review skill; do not mix it into hardening counts or assign it a CVSS-style
severity.
Core rules
- Applicability before compliance. Profile the project and select only controls that match its real build systems, target OSes/arches, threading, prebuild strategy, and vendored dependencies.
- Effective behavior over presence. A flag in one
conditionsbranch, a sanitizer script that never runs in CI, or a.clang-tidywithWarningsAsErrors: ''is not proof the control is effective on the shipped build. - Research globally, report locally. Read the whole
binding.gyp/CMake, CI workflows, scripts, andcommon.gypidefaults to resolve what the compiler actually receives; report only on the requested scope. - Credit toolchain defaults. Mark a control Met when the toolchain or node-gyp
common.gypialready provides it (MSVC/GS,/DYNAMICBASE,/NXCOMPATare on by default; Release builds optimize). Do not flag a default-on protection as missing. - Arch-gate the dangerous flags. Some hardening flags hard-error on the wrong
architecture (
-fcf-protection=fullis x86-only;-mbranch-protectionis arm64-only). Recommending them ungated breaks the build — always require atarget_archcondition. - No cargo-cult controls. Record Not applicable when a control has no relevant surface
(TSan on a strictly single-threaded synchronous addon;
-Wl,-z,*on a macOS-only build), with one-line reasoning. - Sanitizer-aware.
_FORTIFY_SOURCEmust be off in AddressSanitizer builds. Standard-library hardening assertions are independent and may remain enabled unless the project's exact toolchain demonstrates a conflict; a hardening recommendation that breaks the sanitizer build is a Gap, not an improvement. - No auto-apply. Propose changes; edit only when the user explicitly asks.
What ships with it
9 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.
- agents/openai.yaml 222 B
- ATTRIBUTION.md 4.1 KB
- LICENSE 1.2 KB
- references/baseline-and-reporting.md 20 KB
- references/build-and-toolchain.md 20 KB
- references/ci-and-release.md 24 KB
- references/compiler-hardening.md 22 KB
- references/modern-cpp-conventions.md 24 KB
- references/sanitizers-and-analysis.md 26 KB
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.
- 1mo ago First seen · 235 lines · 170 tokens per session scan A db3c1a3fb513
project-setup is a skill published in the GitHub repository photostructure/coding-skills (4 stars, last pushed 13d ago), licensed MIT. It adds 170 tokens to every session and 3,059 once invoked, about $0.0007 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
esp32-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…
phx-review
Review changed Elixir/Phoenix code read-only. Check requirements, cite evidence, deduplicate findings, and return a severity-based verdict.
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
fec-refactor-clean
A safe cleanup workflow for unused front-end code, exports, routes, components, and dependencies.