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/steipete/agent-rules/swift-argument-parsergit clone --depth 1 https://github.com/steipete/agent-rulesWhat 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.07982 |
| Opus 5 | $0.00000 | $0.03991 |
| Sonnet 5 | $0.00000 | $0.01596 |
| Haiku 4.5 | $0.00000 | $0.00798 |
Grade A, and why
swift-argument-parser 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- swift-argument-parser — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 738 lines — stays where its author put it; the contents beside it link to each section on GitHub.
https://swiftpackageindex.com/apple/swift-argument-parser/1.5.1/documentation/argumentparser llms-full.txt
Swift Argument Parser
Framework
ArgumentParser
Straightforward, type-safe argument parsing for Swift.
Overview
By using ArgumentParser, you can create a command-line interface tool by declaring simple Swift types. Begin by declaring a type that defines the information that you need to collect from the command line. Decorate each stored property with one of ArgumentParser‘s property wrappers, declare conformance to ParsableCommand, and implement your command’s logic in its run() method. For async renditions of run, declare AsyncParsableCommand conformance instead.
import ArgumentParser
@main
struct Repeat: ParsableCommand {
@Argument(help: "The phrase to repeat.")
var phrase: String
@Option(help: "The number of times to repeat 'phrase'.")
var count: Int? = nil
mutating func run() throws {
let repeatCount = count ?? 2
for _ in 0..<repeatCount {
print(phrase)
}
}
}
When a user executes your command, the ArgumentParser library parses the command-line arguments, instantiates your command type, and then either calls your run() method or exits with a useful message.
Additional Resources
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 · 738 lines · 0 tokens per session scan A 606b057f59ae
swift-argument-parser is a cursor rule published in the GitHub repository steipete/agent-rules (5,696 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,982 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-30.
Other cursor rules, from other repositories
android_unit_testing_bdd
Unit testing best practices with BDD style.
android_general_rules
For every Kotlin Android code you generate or refactor.
android_integration_testing
Android Integration Testing best practices for multi-layer testing.
android_workmanager_best_practices
Best practices for WorkManager usage in background tasks.
android_naming_conventions
Naming conventions for consistency.
react_hooks
React Hooks best practices for frontend package.