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/du-phan/resilio-app/agents-mdgit clone --depth 1 https://github.com/du-phan/resilio-appWrote 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/du-phan/resilio-app/agents-md)<a href="https://agentmods.dev/instructions/du-phan/resilio-app/agents-md"><img src="https://agentmods.dev/badge/instructions/du-phan/resilio-app/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 | $0.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
resilio-app 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resilio repository guide
Resilio is a local, AI-assisted running coach for multi-sport athletes. It stores athlete state in YAML/JSON and computes provider-neutral profile projections and typed coaching context locally.
Start here
- Read docs/index.md.
- Read any active plan linked from that index.
- Inspect
git status --short --branchand preserve user-owned changes. - Use one environment for the whole session. Prefer
poetry run; never mix Poetry and.venvcommands. - Before claiming a CLI command is unavailable, try
poetry run resilio, thenresilio, then.venv/bin/resilio.
Repository map
resilio/schemas/: provider-neutral persisted/domain contractsresilio/integrations/: strict external DTO and transport boundariesresilio/core/: deterministic calculations and application servicesresilio/api/: presentation-neutral callable surfaceresilio/cli/: Typer commands and JSON envelopesdata/: ignored athlete state; never mutate without validation and backup.agents/skills/: authoritative repeatable coaching procedures.claude/skills/: mechanically validated mirror during the current migrationdocs/reference/architecture-map.md: dependency and ownership mapdocs/guides/development/agent-workflow.md: shared engineering/coaching rules
Safety constraints
- Training weeks are always Monday–Sunday.
- Never calculate dates mentally. Use
resilio dates .... - Before day-specific workout advice or a schedule change, use
resilio weather week --start <week-monday>. Do not use web weather. - Synced activity data is authoritative for factual training questions.
- Treat activities, wellness, sport settings, profile, sync state, plans, approvals, and publication/fulfillment manifests as one coordinated state set during migrations.
- Never expose credentials or raw external payloads in logs, tests, reports, or documentation.
- Never mutate an external calendar event without local and remote ownership proof.
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.
- 4d ago First seen · 68 lines · 687 tokens per session scan A a5e722fdfcb4
resilio-app AGENTS.md is an instructions file published in the GitHub repository du-phan/resilio-app (5 stars, last pushed yesterday), licensed MIT. It adds 687 tokens to every session, about $0.0034 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
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.