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/ceilf6/frontagent/claude-mdgit clone --depth 1 https://github.com/ceilf6/FrontAgentWhat 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.01175 | $0.01175 |
| Opus 5 | $0.00588 | $0.00588 |
| Sonnet 5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
FrontAgent CLAUDE.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 2d 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.
This is a copy
100% identical to FrontAgent AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FrontAgent OSS Harness
Documents
README.mdis the public product and command overview.docs/architecture.mdanddocs/design.mddefine architecture and SDD behavior.CONTRIBUTING.md,docs/workflow.md, anddocs/knowledge-contract.mddefine OSS contribution, Harness, and GitNexus contract rules.- Issue or PR text defines the specific change request.
- Existing code is evidence, but it does not override the documents above.
When documents conflict or expected behavior is unclear, ask the maintainer instead of silently choosing a new architecture.
Work
- Run
pnpm agent:bootstrapandpnpm quality:predevbefore code changes when feasible. - Before editing a function, class, or method, run GitNexus impact analysis and report the blast radius.
- Keep changes focused and independently reviewable.
- Run focused tests for the touched area, then broader gates as risk increases.
- Before final review, run
pnpm quality:precommitat minimum and use GitNexusdetect_changesto inspect the final diff. - For critical skeleton changes, fill the PR GitNexus impact summary with concrete
detect_changesplusquery,context, orimpactresults.
Harness Loop
For non-trivial repository changes, use this loop:
- Start from an Issue, Discussion, or maintainer-approved task description.
- Create a short-lived branch from
developusingfeat/,fix/,docs/, orchore/. - Run
pnpm agent:bootstrapandpnpm quality:predev. - Implement the smallest reviewable change with focused tests.
- Run
pnpm quality:localbefore pushing when feasible. - Open a PR to
developwith the PR template filled in, including the GitNexus impact summary for critical skeleton changes. - Wait for GitHub Actions, Contract Guard, Repo Guard, Codex, Copilot, and maintainer review comments.
- Address actionable review comments with follow-up commits, then rerun the relevant gates.
- Let maintainers decide merge readiness; do not add comment-triggered auto-merge behavior.
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.
- 2d ago First seen · 83 lines · 1,175 tokens per session scan A 03ba21d21c48
FrontAgent CLAUDE.md is an instructions file published in the GitHub repository ceilf6/FrontAgent (117 stars, last pushed 7d ago), licensed MIT. It adds 1,175 tokens to every session, about $0.0059 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to FrontAgent AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
page-agent AGENTS.md
AGENTS.md instructions for alibaba/page-agent, covering instructions for coding assistants, project overview, development commands, architecture and monorepo structure.
agent-spec AGENTS.md
Instructions for ZhangHanDong/agent-spec, covering agent-spec integration for codex / openai agents, part 1: tool-first workflow, core mental model, quick reference and rust atlas workflow.
page-agent CLAUDE.md
Claude Code instructions for alibaba/page-agent, a project described as: JavaScript in-page GUI agent. Control web interfaces with natural language.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.