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 rules/zackiles/deno-kit/with-command-filegit clone --depth 1 https://github.com/zackiles/deno-kitWhat 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.00572 |
| Opus 5 | $0.00000 | $0.00286 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
with-command-file 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions For Reading and Modifying Command Files In src/commands
Before you read or modify any files in src/commands ensure you read and understand how command files work by doing the following:
- Review how commands are loaded and executed in cli.ts
- Review how commands are routed and arguments handled
- Command file names map to CLI commands. Examples:
src/commands/version.tsmaps todeno run -A src/main.ts versionordeno task dev versionif you're in development mode - Commands can configure and use optional arguments. Examples:
src/commands/version.tsmaps todeno run -A src/main.ts some-command --verboseordeno task dev some-command --verboseif you're in development mode
- Command file names map to CLI commands. Examples:
- Review how commands can import and utilize any of the app config in config.ts
- Review the entrypoint of the application in main.ts which calls cli.ts which further invokves one of the commands in
src/commands - Review the general commands available (shown as Deno Tasks) in deno.json
- If you haven't already, review the project readme in README.md to understand the overall application architecture
- CREATING NEW COMMANDS: Review the example template command in the file example.disabled.ts
Involved Files
- main.ts : Entry point for the CLI. Initializes global app config and state before executing
cli.ts - cli.ts : Loads commands with
command-router.tsand executes them - command-router.ts : Configures commands
- example.disabled.ts : Example template command for reference
Extra Related Utilities
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 · 33 lines · 0 tokens per session scan A 32dbdf3eceae
with-command-file is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 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 cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
docs
This file provides guidelines for working with the documentation in the /docs directory.
architecture
Architecture of openapi-to-cli (ocli).
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.