Borrowing it
Nothing to install: this file belongs to Solismuchengxue/skill_swift_cycle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Solismuchengxue/skill_swift_cycle/main/AGENTS.mdgit clone --depth 1 https://github.com/Solismuchengxue/skill_swift_cycleWrote 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/solismuchengxue/skill_swift_cycle/agents-md)<a href="https://agentmods.dev/instructions/solismuchengxue/skill_swift_cycle/agents-md"><img src="https://agentmods.dev/badge/instructions/solismuchengxue/skill_swift_cycle/agents-md.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.1 | $0.00908 | $0.00908 |
| Opus 5 | $0.00454 | $0.00454 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
skill_swift_cycle 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 today.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
These instructions apply to the skill_swift_cycle repository.
Repository purpose
- Maintain one portable Agent Skill for lightweight project governance.
- Keep the canonical package under
skills/swift-cycle/. - Do not add scripts, dependencies, generated assets, or vendor-specific copies unless a verified compatibility requirement justifies them.
Naming
- Separate words in project, repository, and project-root names with
_; do not impose a letter-case rule beyond the chosen project name. - Keep the standards-defined Skill identifier, package directory, and invocation as
swift-cycle; Agent Skills names do not permit underscores. - Treat external syntax constraints as explicit exceptions rather than changing the repository naming rule.
Change rules
- Read
README.md,DESIGN.md, the canonicalSKILL.md, and relevant compatibility documentation before editing. - Preserve user changes and keep each modification traceable to the current request.
- Prefer a small shared-core change over duplicated agent-specific implementations.
- Keep the Skill body concise, imperative, and below 500 lines.
- Keep knowledge-promotion and state-separation guidance project-agnostic and lightweight; do not encode project-specific workflows, mandatory state fields, or fixed status schemas.
- Keep scenario routes and document profiles progressive:
minimalmust remain usable withoutstandardorruntime_integrationartifacts. - Keep Swift Cycle inside one project's engineering loop. Do not add portfolio routing, reviewer creation, capacity management, organizational acceptance, external registries, or cross-project runtime authorization.
- Treat templates as optional structures whose prose is adapted to the resolved file language. Do not create duplicate language-specific template trees.
- Keep the Blueprint as one shared tracked project-intent authority: new projects default to
docs/blueprint.md, root-level Blueprint files are forbidden by default, and complete brownfield equivalents are mapped rather than copied. - Keep Review Packets frozen and date- or milestone-bound; they must not become mutable current-truth documents.
- Do not add unsupported host claims; verify current behavior against first-party documentation.
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.
- today Changed 3b299a315961
- 2d ago Changed · +14 tokens per session ea93e94201ed
- 7d ago First seen · 66 lines · 894 tokens per session scan A 49221f35fca7
skill_swift_cycle AGENTS.md is an instructions file published in the GitHub repository Solismuchengxue/skill_swift_cycle (2 stars, last pushed today), licensed MIT. It adds 908 tokens to every session, about $0.0045 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
ai-agent-rules-generator ui-design.instructions.md
Glitch Payment Gateway admin UI design rules — mandatory element & component reference for WooCommerce settings.
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).