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 instructions/azure/azure-functions-skills/cligit clone --depth 1 https://github.com/Azure/azure-functions-skillsWrote 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/instructions/azure/azure-functions-skills/cli)<a href="https://agentmods.dev/instructions/azure/azure-functions-skills/cli"><img src="https://agentmods.dev/badge/instructions/azure/azure-functions-skills/cli.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.00302 | $0.00302 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
azure-functions-skills cli.instructions.md 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
CLI Development Rules
Usability First
- The CLI is designed with usability as the top priority.
- Commands must be intuitive — users should never feel lost or confused.
- Error messages must be specific and actionable: tell the user what went wrong and what to do next.
- Provide helpful defaults so common workflows require minimal flags.
Output
- Keep output concise and scannable.
- Use color and formatting consistently (success = green, error = red, warning = yellow).
- Progress indicators for long-running operations.
- Respect
--quietand--jsonflags where applicable.
After Changes
- Always compile:
npm run compile - Run unit tests:
npm test - E2E verification is mandatory: test the actual CLI command in an isolated workspace.
node bin/azure-functions-skills.js <cmd> --dir <isolated-workspace> - Never run
setuporchatfrom the repo root — it pollutes the working tree.
Architecture
- CLI entry point:
bin/azure-functions-skills.js - Domain modules:
src/doctor/,src/setup/,src/build/ - Keep option parsing in
bin/; keep business logic insrc/. - Separate concerns — do not mix I/O, validation, and domain logic in one function.
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 · 37 lines · 302 tokens per session scan A 8622fb225912
azure-functions-skills cli.instructions.md is an instructions file published in the GitHub repository Azure/azure-functions-skills (16 stars, last pushed 6d ago), licensed MIT. It adds 302 tokens to every session, about $0.0015 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.