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 tech-radargit 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/tech-radar)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/tech-radar"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/tech-radar.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.00118 | $0.00897 |
| Opus 5 | $0.00059 | $0.00449 |
| Sonnet 5 | $0.00024 | $0.00179 |
| Haiku 4.5 | $0.00012 | $0.00090 |
Grade A, and why
tech-radar 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Radar: Stack Update Scanner
Checks for latest versions, breaking changes, deprecations, and security advisories across the user's core stack.
Core Stack to Monitor
Example only, replace with your own stack. The table below reflects one project's dependencies (a JS/TS stack). The skill detects your actual dependencies from the project manifest at runtime (
package.json,requirements.txt,go.mod,composer.json, etc., see the description); this table is just a fallback of well-known packages to watch.
| Category | Packages |
|---|---|
| Frontend | nuxt, vue, next, react, tailwindcss, formkit, pinia |
| Backend | @nestjs/core, express, fastify |
| Database | prisma, @prisma/client, knex, better-auth |
| Testing | vitest, @vue/test-utils, @testing-library/react |
| Mobile | expo, react-native, nativewind |
| AI | ai (vercel ai-sdk), @ai-sdk/openai, @ai-sdk/anthropic |
| CLI | commander, chalk, ora, inquirer |
| Build | typescript, tsup, turbo, vite |
| Cloud | @aws-sdk/client-s3, @aws-sdk/client-ec2 |
Execution Steps
-
Parse arguments: If user specified a package/framework, focus on that. Otherwise scan full stack.
-
Check latest versions using WebSearch:
- Search:
"{package} latest version {current_year}" - Compare against currently installed version (check the project manifest:
package.json,requirements.txt,go.mod,composer.json, etc.) - Flag major version bumps (potential breaking changes)
- Search:
-
Check for breaking changes:
- For major version bumps: search
"{package} v{new_major} migration guide" - Summarize key breaking changes that affect our patterns
- Cross-reference against known patterns in MEMORY.md
- For major version bumps: search
-
Check security advisories:
- Search:
"{package} CVE {current_year}"or"{package} security advisory" - Flag any HIGH or CRITICAL severity issues
- Search:
-
Check deprecations:
- Search:
"{package} deprecated features {current_year}" - Note any APIs we currently use that are deprecated
- Search:
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 · 80 lines · 118 tokens per session scan A 4c1f5d4d1cd5
tech-radar is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 27d ago), licensed MIT. It adds 118 tokens to every session and 897 once invoked, about $0.0006 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
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.