diagnostic

diagnostic is a skill for Claude Code, Codex from ai-swiss/base. It costs 37 tokens per session (1,133 once invoked), scanned A, original, Apache-2.0.

A guided conversation for finding work tasks that could benefit from AI and deciding which to prioritize. It starts by exploring the user's job, team size, repeated work, documents, and frustrations.

In plain words
What is it for?
Use it to identify repetitive or time-consuming work and assess which tasks are good candidates for automation.
Why use it?
It helps when you know AI might help but do not know where to begin. The questions turn vague interest into a list of concrete tasks to evaluate.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ai-swiss/base/diagnostic
Any agent
npx skills add ai-swiss/base --skill diagnostic
Clone the repo
git clone --depth 1 https://github.com/ai-swiss/base

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for diagnostic

README.md
[![agentmods](https://agentmods.dev/badge/skills/ai-swiss/base/diagnostic.svg)](https://agentmods.dev/skills/ai-swiss/base/diagnostic)
Your own site
<a href="https://agentmods.dev/skills/ai-swiss/base/diagnostic"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/diagnostic.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,133 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.01133
Opus 5 $0.00018 $0.00566
Sonnet 5 $0.00007 $0.00227
Haiku 4.5 $0.00004 $0.00113

Measured 5d ago against content hash 61194b3f2b9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

diagnostic 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 5d 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.

.ai/agents/createur-agent/skills/processes/diagnostic/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Diagnostic: par où commencer avec l'IA?

Aider l'utilisateur à repérer les tâches où un assistant IA aurait le plus d'impact dans son quotidien. Ce process précède la création d'un agent: c'est l'étape préalable.

Inputs

Demande à l'utilisateur:

  • Son métier ou activité: que fait son entreprise?
  • Sa taille: seul, petite équipe, PME?

Pas besoin de plus: le diagnostic se construit au fil de la conversation.

Étapes

1. Explorer le quotidien

Commence par des questions ouvertes, une à la fois:

«Décrivez-moi une journée type dans votre travail. Pas les grandes lignes, le concret: les tâches, les documents, les échanges.»

Puis creuse:

  • «Quelles tâches reviennent chaque semaine, presque à l'identique?»
  • «Quels documents rédigez-vous le plus souvent?»
  • «Qu'est-ce qui vous frustre dans votre quotidien? Ce qui prend trop de temps, ce qui est rébarbatif?»
  • «Y a-t-il des tâches que vous repoussez parce qu'elles sont longues ou pénibles?»

Note chaque tâche mentionnée.

«Si je résume, vos principales tâches répétitives sont: [liste]. C'est bien ça? J'en oublie?»

← Reformulation

2. Évaluer le potentiel

Pour chaque tâche identifiée, évalue silencieusement deux critères:

Faisabilité IA (la tâche est-elle structurable?):

  • Suit un processus que l'on peut décrire → haute
  • Aboutit à un document à la structure récurrente → haute
  • Exige un jugement humain de tous les instants → moyenne
  • Repose sur des données sensibles ou des interactions physiques → basse

Impact (quel gain si un assistant la gère?):

  • Fréquente (quotidienne/hebdomadaire) → haut
  • Chronophage (>30 min par occurrence) → haut
  • Source de frustration ou d'erreurs → haut
  • Occasionnelle et rapide → bas

Ne montre pas cette grille à l'utilisateur: elle te sert seulement à prioriser.

3. Proposer les priorités

Présente les 3 meilleures opportunités sous forme de tableau simple:

«D'après ce que vous m'avez décrit, voici les trois tâches où un assistant IA vous aiderait le plus:

Priorité Tâche Pourquoi
1 [tâche] [fréquence + gain concret]
2 [tâche] [fréquence + gain concret]
3 [tâche] [fréquence + gain concret]

Je vous conseille de commencer par la première: un assistant centré sur une seule tâche, que l'on pourra enrichir ensuite. Qu'en pensez-vous?»

Read the full file on GitHub · 111 lines

Changes

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.

  1. 5d ago First seen · 111 lines · 37 tokens per session scan A 61194b3f2b9f

Subscribe to this mod's changes

diagnostic is a skill published in the GitHub repository ai-swiss/base (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 1,133 once invoked, about $0.0002 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.

Related

Other skills, from other repositories