fnox is a secret manager that stores credentials either encrypted in a Git repository or in supported cloud and password-management services. Developers use it to provide secrets to commands and shell sessions across development, continuous integration, and production. The catalogue includes instructions for using fnox.
Borrowing it
Nothing to install: this file belongs to jdx/fnox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jdx/fnox/main/.agents/skills/jouet-init/SKILL.mdgit clone --depth 1 https://github.com/jdx/fnoxWrote 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/jdx/fnox/jouet-init)<a href="https://agentmods.dev/skills/jdx/fnox/jouet-init"><img src="https://agentmods.dev/badge/skills/jdx/fnox/jouet-init/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/jdx/fnox/jouet-init"><img src="https://agentmods.dev/badge/skills/jdx/fnox/jouet-init.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.00045 | $0.01249 |
| Opus 5.5 | $0.00018 | $0.00500 |
| Sonnet 5.5 | $0.00009 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
jouet-init 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize jouet for this project
Help this project's agents use fewer tokens and finish work faster. Find where
jouet fits the existing workflow, configure what is useful, and explain any
gaps. Record the checks you establish in .jouet/project.toml (below), so
every later session starts knowing them; beyond that, a project that needs no
other configuration is a successful outcome.
Understand the project
Read the project instructions, relevant manifests, task definitions, CI and
existing .jouet files. Identify the actual full test command, focused checks,
generated files and any setup they require. Follow the project's task runner;
a task's name alone does not establish what it covers. Read only the files
needed to establish those facts.
Run jouet agent-help and consult jouet agent-help COMMAND --full for the
commands and configuration you need. Use the installed version's help rather
than guessing flags, supported adapters or configuration keys. Hook installation
belongs to jouet setup HARNESS; if the user only asked for a configuration
review, report missing hooks without installing them.
Make costs visible
Read jouet cost for existing build, test and lint timings. If useful session
history exists, use jouet audit scoped to this project to find repeated work,
failed approaches and where tokens and time go. Missing history is a gap to
report, not evidence that the project is cheap or jouet saves nothing.
Use the evidence to recommend when to batch edits before a slow check and which
focused checks help during iteration. Do not start a cold rebuild, full suite,
network-dependent setup or paid agent benchmark just to collect timings. If a
representative check is already appropriate to the user's task, run it through
jouet test so its result and duration are recorded.
Record the checks
Write the commands you established to .jouet/project.toml, to be committed
with the project. The session-start primer shows them to every later session
once a person trusts the repository's jouet files, so agents run the right
check instead of looking for it:
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 · 111 lines · 45 tokens per session scan A a5967da17ad8
jouet-init is a skill published in the GitHub repository jdx/fnox (2,355 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,249 once invoked, about $0.0002 per session on Opus 5.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-11-03.
Other skills, from other repositories
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
cs-escalation-brief
Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…