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/ad-naan/adnify-cli/local-commandsgit clone --depth 1 https://github.com/ad-naan/Adnify-CliWrote 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/ad-naan/adnify-cli/local-commands)<a href="https://agentmods.dev/commands/ad-naan/adnify-cli/local-commands"><img src="https://agentmods.dev/badge/commands/ad-naan/adnify-cli/local-commands.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.00000 | $0.00275 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
local-commands 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 3d 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.
What it actually says
Local Commands
These commands are handled by the CLI itself instead of being sent to the model.
- :help
- :mode chat
- :mode agent
- :mode plan
- :workspace
- :status
- :tools
- :doctor
- :diff
- :review
- :model [provider] [model]
- :config
- :config init
- :config set provider [value] [model]
- :config set model [value]
- :config set api-key [value]
- :config set base-url [value]
- :config set context-window [tokens]
- :config clear api-key
- :language [zh-CN|en]
- :animation [off|minimal|full]
- :permissions [manual|workspace|auto|plan]
- :runtime [show|reset]
- :runtime set [key] [integer]
- :session
- :storage
- :storage set [path]
- :storage reset
- :sessions
- :resume [index|id]
- :memory [content]
- :memory list
- :memory clear
- :checkpoint [message]
- :undo
- :restore [id|index]
- :skill [name|list]
- :mcp
- :context
- :clear
- :exit
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.
- 3d ago First seen · 46 lines · 0 tokens per session scan A a058525bb470
local-commands is a command published in the GitHub repository ad-naan/Adnify-Cli (10 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 275 tokens. 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 commands, from other repositories
commit
Create a git commit for the current staged (or unstaged) changes using a structured commit message convention.
release-notes
Generate release notes for this project and save them to CHANGELOG.md.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.