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/getlytos/lytos-cli/documentationnpx skills add getlytos/lytos-cli --skill documentationgit clone --depth 1 https://github.com/getlytos/lytos-cliWhat 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.00060 | $0.02402 |
| Opus 5 | $0.00030 | $0.01201 |
| Sonnet 5 | $0.00012 | $0.00480 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
documentation 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 yesterday.
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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill — Documentation
This skill defines how to document code, modules, and learnings on a project using Lytos. An agent loaded with this skill knows what to document, in what format, and when to update the project memory.
When to invoke this skill
- After writing or modifying a public function
- After a sprint, to consolidate learnings into the memory
- When creating a new module or component
- To write or update an issue
Code documentation
Universal principle
Every public function and method must be documented. The format depends on the language, the content is the same:
- First line: what the function does (infinitive verb)
- Parameters: type + name + one-sentence description
- Return: type + description, including edge cases (empty list, null, error)
- Errors: each possible exception or error with its condition
Examples by language
def calculer_ttc(prix_ht: float, taux_tva: float) -> float:
"""Calcule le prix TTC à partir du prix HT et du taux de TVA.
Args:
prix_ht: Le prix hors taxes en euros.
taux_tva: Le taux de TVA (ex: 0.20 pour 20%).
Returns:
Le prix TTC arrondi à 2 décimales.
Raises:
ValueError: Si le prix HT est négatif.
"""
/**
* Filtre les produits selon les critères donnés.
*
* @param {Product[]} produits - La liste complète des produits.
* @param {FilterCriteria} criteres - Les critères de filtrage à appliquer.
* @returns {Product[]} Les produits correspondant aux critères. Tableau vide si aucun résultat.
*/
function filtrerProduits(produits, criteres) {
// CalculerTTC calcule le prix TTC à partir du prix HT et du taux de TVA.
// Retourne une erreur si le prix HT est négatif.
func CalculerTTC(prixHT, tauxTVA float64) (float64, error) {
/**
* Calcule le prix TTC à partir du prix HT et du taux de TVA.
*
* @param float $prixHT Le prix hors taxes en euros.
* @param float $tauxTVA Le taux de TVA (ex: 0.20 pour 20%).
* @return float Le prix TTC arrondi à 2 décimales.
* @throws InvalidArgumentException Si le prix HT est négatif.
*/
public function calculerTTC(float $prixHT, float $tauxTVA): float
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.
- yesterday First seen · 344 lines · 60 tokens per session scan A 7818f6df26a4
documentation is a skill published in the GitHub repository getlytos/lytos-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 2,402 once invoked, about $0.0003 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.