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 atournayre/claude-marketplace --skill statusgit clone --depth 1 https://github.com/atournayre/claude-marketplaceWrote 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/atournayre/claude-marketplace/status)<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/status"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/status/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/atournayre/claude-marketplace/status"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/status.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.00014 | $0.00866 |
| Opus 5 | $0.00007 | $0.00433 |
| Sonnet 5 | $0.00003 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
dev:status 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration de sortie
Instructions à Exécuter
IMPORTANT : Exécute ce workflow étape par étape :
IMPORTANT : Cette skill affiche un statut court et nécessite un format de sortie spécifique.
Lis le frontmatter de cette skill. Si un champ output-style est présent, exécute immédiatement :
/output-style <valeur-du-champ>
Note : Une fois que le champ output-style sera supporté nativement par Claude Code, cette instruction pourra être supprimée.
Output-style requis : ultra-concise
Objectif
Afficher l'état actuel du workflow de développement pour que l'utilisateur sache où il en est.
Instructions
- Chercher un fichier
.claude/data/.dev-workflow-state.jsondans le répertoire courant - Si le fichier existe, lire l'état du workflow
- Afficher le plan avec les statuts de chaque phase
Format de sortie
🔄 Workflow de développement
{status} 0. Discover - Comprendre le besoin {duration}
{status} 1. Explore - Explorer codebase {duration}
{status} 2. Clarify - Questions clarification {duration}
{status} 3. Design - Proposer architectures {duration}
{status} 4. Plan - Générer specs {duration}
{status} 5. Code - Implémenter {duration}
{status} 6. Review - QA complète {duration}
{status} 7. Summary - Résumé final {duration}
📋 Feature: "{feature_description}"
📁 Plan: {plan_path}
⏱️ Temps total: {total_duration}
Affichage des durées
Pour chaque phase :
- Si
completedavecdurationMs→ afficher({formatted_duration}) - Si
in_progressavecstartedAt→ afficher(en cours depuis {elapsed}) - Si pas de timing → ne rien afficher
Format de durée
Formater les durées de manière lisible :
< 60s→{X}s(ex:45s)< 60min→{X}m {Y}s(ex:2m 30s)>= 60min→{X}h {Y}m(ex:1h 15m)
Légende des statuts
✅- Phase complétée🔵- Phase en cours (ajouter← En coursà la fin)⬜- Phase à faire
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.
- 11d ago First seen · 115 lines · 14 tokens per session scan A e6115c0b71a9
dev:status is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 866 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.