Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftnpx agentmods add commands/thebeardedbearsas/claude-craft/add-technologyWrote 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/commands/thebeardedbearsas/claude-craft/add-technology)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/add-technology"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/add-technology.svg" alt="Measured on agentmods" 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.00019 | $0.02562 |
| Opus 5 | $0.00010 | $0.01281 |
| Sonnet 5 | $0.00004 | $0.00512 |
| Haiku 4.5 | $0.00002 | $0.00256 |
Grade A, and why
add-technology 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ajouter une Technologie
Vous êtes un expert intégrateur de technologies pour claude-craft. Votre mission est d'ajouter une nouvelle stack technologique en :
- Recherchant les best practices via Context7 MCP et recherche web
- Générant tous les fichiers nécessaires (rules, commands, templates, skills, agents)
- Créant le script d'installation
- Mettant à jour la documentation et la page de présentation
Arguments
$ARGUMENTS
Arguments:
nom-technologie: Nom de la technologie à ajouter (ex: "nextjs", "nestjs", "golang", "laravel")- (Optionnel)
catégorie: Catégorie de la technologie (frontend, backend, mobile, devops, fullstack)
Exemple : /common:add-technology "nestjs" ou /common:add-technology "golang" backend
MISSION
Étape 1 : Analyser la Technologie
Identifier :
- Nom officiel et alias courants
- Type : framework, bibliothèque, langage, outil
- Catégorie : frontend, backend, mobile, devops, fullstack
- Écosystème : outils associés, frameworks de test, options de déploiement
- Public cible : web, mobile, API, CLI, etc.
Étape 2 : Rechercher avec Context7 (MCP)
Utiliser Context7 pour accéder à la documentation officielle :
Interroger Context7 pour :
1. Guide de démarrage officiel
2. Structure de projet recommandée
3. Best practices et design patterns
4. Stratégies de test (unitaire, intégration, e2e)
5. Best practices sécurité
6. Conseils d'optimisation performance
7. Recommandations de déploiement
Informations à Extraire
| Sujet | Détails à Trouver |
|---|---|
| Architecture | Patterns recommandés (MVC, Clean, Hexagonal, etc.) |
| Standards de Code | Guide de style, conventions de nommage, structure des fichiers |
| Outillage | Outils CLI, formateurs, linters, bundlers |
| Tests | Frameworks de test, outils de couverture, stratégies de mock |
| Sécurité | Authentification, autorisation, vulnérabilités courantes |
| Qualité | Analyse statique, vérification de types, pratiques de review |
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 · 294 lines · 19 tokens per session scan A de8516746178
add-technology is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 2,562 once invoked, about $0.0001 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 commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.