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 commands/fujigo-software/f5-framework-claude/f5-langgit clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claudeWrote 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/commands/fujigo-software/f5-framework-claude/f5-lang)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/f5-lang"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/f5-lang.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.00008 | $0.02772 |
| Opus 5 | $0.00004 | $0.01386 |
| Sonnet 5 | $0.00002 | $0.00554 |
| Haiku 4.5 | $0.00001 | $0.00277 |
Grade A, and why
f5-lang 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/f5-lang - Language Preference Command
Set the display language for F5 Framework output.
ARGUMENTS
The user's request is: $ARGUMENTS
OVERVIEW
F5 Framework supports 3 languages:
en- English (default)vi- Tiếng Việtja- 日本語
Language can be set at:
- Global level - User preference across all projects (
~/.f5/preferences.yaml) - Project level - Override for specific project (
.f5/config.json)
STEP 1: PARSE ARGUMENTS
| Pattern | Action |
|---|---|
| (no args) | SHOW_CURRENT |
en or vi or ja |
SET_GLOBAL |
<lang> --project |
SET_PROJECT |
--reset |
RESET_TO_DEFAULT |
ACTION: SHOW_CURRENT
/f5-lang
Show current language settings.
Process:
- Read global preference from
~/.f5/preferences.yaml - Read project preference from
.f5/config.json(if exists) - Determine active language
Check Global Preference:
GLOBAL_LANG="en"
GLOBAL_LANG_NAME="English"
if [ -f ~/.f5/preferences.yaml ]; then
GLOBAL_LANG=$(grep '^language:' ~/.f5/preferences.yaml 2>/dev/null | sed 's/language:[[:space:]]*"\{0,1\}\([^"]*\)"\{0,1\}/\1/')
if [ -z "$GLOBAL_LANG" ]; then
GLOBAL_LANG="en"
fi
fi
case "$GLOBAL_LANG" in
"vi") GLOBAL_LANG_NAME="Tiếng Việt" ;;
"ja") GLOBAL_LANG_NAME="日本語" ;;
*) GLOBAL_LANG_NAME="English" ;;
esac
Check Project Preference:
PROJECT_LANG=""
PROJECT_LANG_NAME="(not set)"
if [ -f ".f5/config.json" ]; then
PROJECT_LANG=$(jq -r '.language // empty' .f5/config.json 2>/dev/null)
if [ -n "$PROJECT_LANG" ] && [ "$PROJECT_LANG" != "null" ]; then
case "$PROJECT_LANG" in
"vi") PROJECT_LANG_NAME="Tiếng Việt" ;;
"ja") PROJECT_LANG_NAME="日本語" ;;
"en") PROJECT_LANG_NAME="English" ;;
esac
else
PROJECT_LANG=""
PROJECT_LANG_NAME="(not set)"
fi
fi
Determine Active Language:
if [ -n "$PROJECT_LANG" ]; then
ACTIVE_LANG="$PROJECT_LANG"
ACTIVE_SOURCE="project (.f5/config.json)"
else
ACTIVE_LANG="$GLOBAL_LANG"
ACTIVE_SOURCE="global (~/.f5/preferences.yaml)"
fi
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 · 442 lines · 8 tokens per session scan A 82334ce217e5
f5-lang is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 2,772 once invoked, about $0.0000 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 commands, from other repositories
build
Guided feature development with approval gates at each phase.
plan
Project spec (no args) or feature FRD (with args).
ship
Autonomous spec-to-PR pipeline with zero approval gates.
debug
Structured debugging with parallel investigation agents.
init
Analyze codebase and generate CLAUDE.md with project conventions.
release
Generate changelog, bump version, and create git tag.