FrontAgent CLAUDE.md

A set of project-specific instructions for FrontAgent, an open-source software project and its development workflow.

In plain words
What is it for?
Use it when changing FrontAgent code, especially to understand the requested design, check affected code, run quality checks, and prepare a focused change.
Why use it?
It keeps coding work aligned with the project's documents, impact checks, tests, and review rules.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/ceilf6/frontagent/claude-md
Clone the repo
git clone --depth 1 https://github.com/ceilf6/FrontAgent
Per session 1,175 This file is loaded in full into every session.
When invoked 1,175 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 03ba21d21c48, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

CLAUDE.md · 83 lines

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

  1. README.md is the public product and command overview.
  2. docs/architecture.md and docs/design.md define architecture and SDD behavior.
  3. CONTRIBUTING.md, docs/workflow.md, and docs/knowledge-contract.md define OSS contribution, Harness, and GitNexus contract rules.
  4. Issue or PR text defines the specific change request.
  5. 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

  1. Run pnpm agent:bootstrap and pnpm quality:predev before code changes when feasible.
  2. Before editing a function, class, or method, run GitNexus impact analysis and report the blast radius.
  3. Keep changes focused and independently reviewable.
  4. Run focused tests for the touched area, then broader gates as risk increases.
  5. Before final review, run pnpm quality:precommit at minimum and use GitNexus detect_changes to inspect the final diff.
  6. For critical skeleton changes, fill the PR GitNexus impact summary with concrete detect_changes plus query, context, or impact results.

Harness Loop

For non-trivial repository changes, use this loop:

  1. Start from an Issue, Discussion, or maintainer-approved task description.
  2. Create a short-lived branch from develop using feat/, fix/, docs/, or chore/.
  3. Run pnpm agent:bootstrap and pnpm quality:predev.
  4. Implement the smallest reviewable change with focused tests.
  5. Run pnpm quality:local before pushing when feasible.
  6. Open a PR to develop with the PR template filled in, including the GitNexus impact summary for critical skeleton changes.
  7. Wait for GitHub Actions, Contract Guard, Repo Guard, Codex, Copilot, and maintainer review comments.
  8. Address actionable review comments with follow-up commits, then rerun the relevant gates.
  9. Let maintainers decide merge readiness; do not add comment-triggered auto-merge behavior.

Read the full file on GitHub · 83 lines

Changes

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.

  1. 2d ago First seen · 83 lines · 1,175 tokens per session scan A 03ba21d21c48

Subscribe to this mod's changes

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.