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/jjmartres/ai-coding-agents/asdfnpx skills add jjmartres/ai-coding-agents --skill asdfgit clone --depth 1 https://github.com/jjmartres/ai-coding-agentsWrote 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/jjmartres/ai-coding-agents/asdf)<a href="https://agentmods.dev/skills/jjmartres/ai-coding-agents/asdf"><img src="https://agentmods.dev/badge/skills/jjmartres/ai-coding-agents/asdf.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.00148 | $0.02175 |
| Opus 5 | $0.00074 | $0.01087 |
| Sonnet 5 | $0.00030 | $0.00435 |
| Haiku 4.5 | $0.00015 | $0.00217 |
Grade B, and why
asdf scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install -y git curl Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sudo apt install -y git curl How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
asdf Version Manager Skill
asdf is a universal CLI version manager — one tool to replace nvm, pyenv, rbenv, tfenv, goenv and more. It manages per-project versions via .tool-versions files and switches versions automatically as you navigate directories.
When to Use This Skill
Use this skill when the user is:
- Installing or setting up asdf on a new machine (any OS, any shell)
- Adding plugins for a language or tool (Node.js, Python, Go, Terraform, kubectl, Helm, etc.)
- Installing or switching versions of any tool managed by asdf
- Managing
.tool-versionsfiles — creating, editing, or understanding version resolution - Migrating from single-language version managers like nvm, pyenv, rbenv, goenv, tfenv, or sdkman
- Configuring shell integration for Bash, Zsh, Fish, or Elvish
- Debugging version resolution — wrong version active, shims not working,
command not founderrors - Onboarding to a project that uses
.tool-versionsfor reproducible environments - Setting up CI/CD pipelines that need deterministic tool versions via asdf
- Configuring
.asdfrcfor legacy file support, concurrency, or plugin repository settings
Core Concepts
- Plugin: Adapter for a specific tool (nodejs, python, terraform, kubectl, etc.)
- Tool: The actual runtime/binary managed (e.g., Node.js 20.11.0)
- .tool-versions: Project-level file declaring exact versions; asdf resolves it by traversing up the directory tree to
$HOME - Shims: Lightweight wrappers in
~/.asdf/shims/that intercept tool invocations and dispatch to the right version - Version scopes: project (
.tool-versionsin cwd) → parent dirs →$HOME/.tool-versions→ env varASDF_${TOOL}_VERSION
Installation
Dependencies (all platforms)
# Debian/Ubuntu
sudo apt install -y git curl
# macOS
brew install git curl
Install asdf binary (recommended: binary download)
# Download latest release from https://github.com/asdf-vm/asdf/releases
# Or via git clone (classic method):
git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.16.7
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 · 272 lines · 148 tokens per session scan B 88efb80f1be0
asdf is a skill published in the GitHub repository jjmartres/ai-coding-agents (44 stars, last pushed 2mo ago), licensed MIT. It adds 148 tokens to every session and 2,175 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…