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 agentmods add skills/ai-swiss/base/comprendre-basenpx skills add ai-swiss/base --skill comprendre-basegit clone --depth 1 https://github.com/ai-swiss/baseWrote 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/ai-swiss/base/comprendre-base)<a href="https://agentmods.dev/skills/ai-swiss/base/comprendre-base"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/comprendre-base.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 | $0.00039 | $0.01030 |
| Opus 5 | $0.00019 | $0.00515 |
| Sonnet 5 | $0.00008 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
comprendre-base 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprendre BASE
Expliquer BASE à la bonne profondeur, en lisant d'abord la doc canonique. Ce process est lui-même une démonstration du modèle BASE: agent → process → ressources référencées → réponse fondée → action suivante.
Méthode
- Repère le profil si utile: débutant, équipe, architecte, sécurité/IT, développeur.
- Repère le sujet: vision, architecture, routage, policy, MCP, racines/workspace, données/sécurité.
- Ouvre les sources canoniques listées pour ce sujet.
- Réponds dans la langue et à la profondeur de l'utilisateur.
- Dis ce que cela change pour sa tâche en cours, s'il en a une.
- Propose une action suivante, ou de revenir à la tâche interrompue.
Sources à lire selon le sujet
- Vision / pourquoi:
docs/learn/co-penser-avec-lia.md(le pourquoi: vérification, pertes de contrôle, méthode), commence iciMANIFESTO.mddocs/learn/pratiques-co-pensee.mddocs/learn/comprendre.md
- BASE et les autres outils, agents planifiés ou autonomes:
docs/reference/base-et-vos-outils-ia.md(dont «Agents planifiés et autonomes»: logique dans BASE, exécution par la plateforme, humain au point de validation; et «Pour votre outil précis: demandez à BASE»)- pour une intégration concrète à un outil donné, suis le process
integrer-un-outil
- Architecture / modèle / six plans:
docs/learn/comprendre.md(section «L'architecture en six plans»)docs/reference/framework-public.mdspecs/current/00_overview/vision.md
- Routage agent → process → ressources:
docs/reference/routage-process-et-ressources.mdspecs/current/10_core/routing.md
- Permissions / policy / frontières:
docs/trust/securite-et-limites.mdspecs/current/10_core/policy.md
- Données / sécurité (ce qui sort, ce qui est prouvé):
docs/trust/frontiere-local-vs-sortant.mddocs/trust/mecanismes-verifies.md
- Racines / workspace / MCP:
specs/current/10_core/cli.mdspecs/current/10_core/mcp.md
Profondeur selon le profil
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.
- 5d ago First seen · 83 lines · 39 tokens per session scan A e1ceba01ca3e
comprendre-base is a skill published in the GitHub repository ai-swiss/base (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 1,030 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.
Other skills, from other repositories
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
escalation-governance
Assess whether to escalate models. Use when evaluating reasoning depth.
implementing-iso-27001-information-security-management
ISO/IEC 27001:2022 is the international standard for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). This skill covers the complete.
agt-policy-authoring
Create and validate a minimal AGT Copilot CLI policy tailored to the repository being inspected.
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.12.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
TRX Staking & SR Voting
Stake TRX, vote for Super Representatives, and claim voting rewards on TRON.