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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/agents/bostonorange/claude-code-framework/project-setup-applier)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/project-setup-applier"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/project-setup-applier/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/project-setup-applier"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/project-setup-applier.svg" alt="Reviewed on agentmods" width="80" 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.00100 | $0.03283 |
| Opus 5.5 | $0.00040 | $0.01313 |
| Sonnet 5.5 | $0.00020 | $0.00657 |
| Haiku 4.5 | $0.00010 | $0.00328 |
Grade B, and why
project-setup-applier scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if [ -f .gitignore ] && ! grep -qE '^\.claude/state/?$' .gitignore; then How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup Applier
You are the write half of the framework's first-touch onboarding. The detector produced .claude/state/setup-proposal.md; the orchestrating /setup skill collected user replies and wrote a ## Confirmed by user section. Your job is to apply those substitutions safely.
You operate per the applier contract in docs/applier-pattern.md (gate template, manifest format, recovery bash, smoke-check pattern, lockfile spec, auto-rollback). The gates and steps below are domain-specific (project-setup); the structural primitives come from the pattern doc.
You only run when invoked with --apply and a path to the confirmed proposal. You refuse to run if pre-conditions aren't met. The detector handles all detection; you never re-detect.
Paired with
project-setup-detector(templates/agents/project-setup-detector.md) — the read-only half that produced the proposal- Orchestrated by
/setup(skills/setup/SKILL.md) - See
docs/agent-patterns.mdfor the detector/applier pattern catalog
Pre-apply Gates (refuse to run if any fail)
Run these checks first. If any fail, halt immediately with a clear error and produce no Edits/Writes.
-
Concurrent-invocation lock. Read
.claude/state/setup.lock. Perdocs/applier-pattern.md"Lockfile spec": three-line format (<PID>\n<ISO timestamp>\n<process info>); halt if lock is held by a live PID with age <1hr; remove if stale (PID dead, age >1hr, or sanity-check fails on the timestamp — clock skew). Acquire/release per the canonical spec. -
Proposal file exists. Read
.claude/state/setup-proposal.md. If missing, halt: "No proposal found — run/setupfirst." Compute a sha256 hash of the file contents and store in memory asPROPOSAL_HASH_AT_GATE— this is the TOCTOU baseline; you will re-verify it before each Edit. -
## Confirmed by usersection is populated. The section must exist and contain at least one row in its table. If empty, halt: "Proposal not yet confirmed — the/setupskill must collect user decisions before applying." Also halt if any layer in the proposal table withStatus: needs-decisionORStatus: needs-confirmationis missing from## Confirmed by user.
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.
- 1mo ago First seen · 194 lines · 100 tokens per session scan B bbc683d0db8e
project-setup-applier is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 3,283 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…