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 markshust/hcf --skill project-setupgit clone --depth 1 https://github.com/markshust/hcfWrote 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/markshust/hcf/project-setup)<a href="https://agentmods.dev/skills/markshust/hcf/project-setup"><img src="https://agentmods.dev/badge/skills/markshust/hcf/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/markshust/hcf/project-setup"><img src="https://agentmods.dev/badge/skills/markshust/hcf/project-setup.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.00033 | $0.02844 |
| Opus 5.5 | $0.00013 | $0.01138 |
| Sonnet 5.5 | $0.00007 | $0.00569 |
| Haiku 4.5 | $0.00003 | $0.00284 |
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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One-time interactive setup to configure a project for autonomous development.
Purpose
Create CLAUDE.md and all project configuration files in .claude/ through an interactive process with auto-detection.
Execution Steps
Step 1: Check for Existing Configuration
First, check if configuration already exists:
ls CLAUDE.md .claude/testing.md .claude/code-standards.md .claude/architecture.md 2>/dev/null
If CLAUDE.md and all 3 config files (testing.md, code-standards.md, architecture.md) exist, inform the user:
Project already configured. CLAUDE.md and config files exist in
.claude/. To reconfigure, delete CLAUDE.md and.claude/then run/project-setupagain.
Otherwise, continue with setup.
Step 2: Auto-Detect Project Type
Scan the project root for configuration files to detect the tech stack:
Check for these files (in parallel):
composer.json→ PHP/Laravel/Symfonypackage.json→ Node.js/React/Vue/Next.jsCargo.toml→ Rustgo.mod→ Gopyproject.tomlorrequirements.txt→ PythonGemfile→ Ruby/Railspom.xmlorbuild.gradle→ Java*.csprojor*.sln→ .NET
For each detected file, extract:
- Framework and version
- Testing framework (from devDependencies or test config)
- Linting/formatting tools
Example auto-detection output:
Detected project configuration:
- Framework: Laravel 11 (from composer.json)
- PHP Version: 8.3
- Testing: Pest PHP (from composer.json require-dev)
- Linting: Laravel Pint (from composer.json require-dev)
Step 3: Confirm Detection
Ask user to confirm detected configuration:
I detected the following. Is this correct? (y/n) [Show detected config]
If incorrect, ask clarifying questions about each incorrect item.
Step 4: Gather Additional Information
Ask these questions (skip if already detected):
Q1: Test Command
What command runs your tests? Detected:
./vendor/bin/pest[Enter to confirm or type custom]
Q1b: Parallel Test Command
Does your test runner support parallel execution? If so, what's the command? (e.g.,
./vendor/bin/pest --parallel,npm test -- --parallel,pytest -n auto,go test ./... -parallel 4) [Enter detected parallel command, type custom, or 'none' if not supported]
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 · 356 lines · 33 tokens per session scan A 3ae5c478315d
project-setup is a skill published in the GitHub repository markshust/hcf (82 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 2,844 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
feature-dev
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an…
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
test-genius
Use when writing tests, increasing coverage, verifying functionality, or implementing TDD — before claiming any feature or fix is complete.
abd-test
ABD Testing agent: auto-detects the test framework, writes tests matching project style, runs the suite, and records a test artifact.
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
unity-testing
Unity 6 testing guide. Use when writing unit tests, integration tests, or doing TDD with Unity Test Framework. Covers Edit Mode and Play Mode tests, NUnit attributes ([Test], [UnityTest], [SetUp], [TearDown]), testing MonoBehaviours and coroutines, and CI/CD integration. Based on Unity 6.3 LTS documentation.