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 faizkhairi/claude-code-blueprint --skill register-projectgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/register-project)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/register-project"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/register-project.svg" alt="Measured on agentmods" 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.00052 | $0.00305 |
| Opus 5 | $0.00026 | $0.00152 |
| Sonnet 5 | $0.00010 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
register-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 8d 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
Register Project in memory
Step 1: Detect Project Info
Gather from the current working directory or user input:
- Project name and path
- Framework/language (check package.json, pyproject.toml, composer.json, etc.)
- Test command (check scripts in package manager config)
- Git remote URL
- Current test count (run tests and count)
Step 2: Read Template
Read ./memory/templates/coding-template.md for the standard format.
Step 3: Check Capacity
Scan ./memory/projects/active/. If 10+ projects exist, identify the oldest by Last Accessed date and suggest archiving it.
Step 4: Create Project File
Write to ./memory/projects/active/{project-name}.md using the template, filled with detected info.
Step 5: Confirm
Show the created file path and key fields to the user.
Rules
- Never overwrite an existing project file; read it first and update if it exists
- Use the template format exactly
- Set Last Accessed to today's date
- Leave Session Context section with placeholder (populated during actual work)
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.
- 8d ago First seen · 39 lines · 52 tokens per session scan A 596046f5e3eb
register-project is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 27d ago), licensed MIT. It adds 52 tokens to every session and 305 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-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.