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/gaelic-ghost/swiftasb/agents-mdgit clone --depth 1 https://github.com/gaelic-ghost/SwiftASBWhat 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.03537 | $0.03537 |
| Opus 5 | $0.01768 | $0.01768 |
| Sonnet 5 | $0.00707 | $0.00707 |
| Haiku 4.5 | $0.00354 | $0.00354 |
Grade A, and why
SwiftASB AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Repo-local guidance for maintaining SwiftASB, a Swift Package Manager library that wraps the local Codex app-server for Swift and SwiftUI clients.
Repository Scope
What This File Covers
- Use this file for all work at the SwiftASB repository root.
- Treat this package as a library first: public API should be deliberate, documented, and tested.
- Use Swift Package Manager as the source of truth for package structure, dependencies, products, targets, resources, and Swift language mode.
- Treat the bundled Codex app-server v2 schema as the primary generated-wire source of truth.
- Treat the generated wire layer as internal scaffolding, not the final public Swift API.
Where To Look First
- Start with
Package.swiftfor package graph, target, dependency, platform, and Swift language mode changes. - Use
Sources/SwiftASB/Public/for public API shape andSources/SwiftASB/Protocol/,Sources/SwiftASB/Transport/, andSources/SwiftASB/History/for the main internal runtime surfaces. - Use
Sources/SwiftASB/Generated/CodexWire/Latest/for the promoted generated v2 wire snapshot. - Use
Tests/SwiftASBTests/for Swift Testing coverage. - Use
scripts/generate-wire-types.shfor Codex schema-derived wire refreshes. - Use
scripts/repo-maintenance/for repo-owned validation, shared sync, and release entrypoints. - Use
README.md,CONTRIBUTING.md,ROADMAP.md, anddocs/maintainers/for shipped behavior, contributor workflow, planned work, and durable design decisions.
Working Rules
Change Scope
- Prefer the simplest correct Swift that is easiest to read, reason about, and maintain.
- Prefer value types for domain modeling.
- Prefer concrete types internally and reserve protocols for real seams.
- Mark classes
finalby default when reference semantics are required. - Keep dependency flow unidirectional and ownership obvious.
- Prefer explicit, consistent, and unambiguous names.
- Prefer synthesized conformances and memberwise initialization whenever they satisfy the real need.
- Avoid ceremony, wrappers, or extra abstraction layers unless they solve a concrete package problem.
- Keep operator-facing errors, warnings, and log strings descriptive and human-readable.
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 · 215 lines · 3,537 tokens per session scan A afc26001d9ba
SwiftASB AGENTS.md is an instructions file published in the GitHub repository gaelic-ghost/SwiftASB (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,537 tokens to every session, about $0.0177 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-31.
Other instructions, from other repositories
Peekaboo AGENTS.md
AGENTS.md instructions for openclaw/Peekaboo, covering repository guidelines, start here, project structure & modules, build, test, and development commands and coding style & naming conventions.
codex-provider-sync AGENTS.md
Instructions for Dailin521/codex-provider-sync, covering ai / agent operator guide, vnext architecture baseline, goal, choose the interface and safe operating flow.
Applite CLAUDE.md
Instructions for milanvarady/Applite, covering claude.md, project overview, build & run, architecture and data flow.
palmier-pro AGENTS.md
AGENTS.md instructions for palmier-io/palmier-pro, covering palmierpro, build, agents, engineering approach and code style.
scarf AGENTS.md
Instructions for awizemann/scarf: This repo carries its own agent memory — plain files in git, served by the in-repo memophant-mcp MCP server, managed by the Memophant macOS app. It works the same for every agent (Claude Code, Codex, Cursor, Gemini, Copilot). This block is regenerated between the memophant markers…
scarf copilot-instructions.md
Instructions for awizemann/scarf: File memory notes under one of six folders (architecture/conventions/decisions/operations/project/roadmap), never the root. When a note is grounded in code, pass sourcepaths (the repo files it depends on) so Memory Health can drift-check it — an unanchored code note can't be kept…