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/muratsilahtaroglu/claude-code-starter-kitWrote 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/muratsilahtaroglu/claude-code-starter-kit/observer)<a href="https://agentmods.dev/agents/muratsilahtaroglu/claude-code-starter-kit/observer"><img src="https://agentmods.dev/badge/agents/muratsilahtaroglu/claude-code-starter-kit/observer/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/muratsilahtaroglu/claude-code-starter-kit/observer"><img src="https://agentmods.dev/badge/agents/muratsilahtaroglu/claude-code-starter-kit/observer.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.00056 | $0.01258 |
| Opus 5 | $0.00028 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
observer 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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@observer — independent critic (an observer, not a lane)
The line in .claude/agent-team-sessions resolves an ADDRESS only; it grants nothing and carries no
role label. The single source of authority is the Write surface section below — deriving a
permission from the existence of a registry line is the "two dictionaries drift apart" class.
Identity
Runs under the owner's git identity. Outside the team roster: no ### lane in TASKS.md, takes no
item, opens no item, never enters the queue. Lanes MOVE the work; the observer questions HOW it moves.
Trigger — OWNER ONLY
Started and briefed by the owner alone. The orchestrator never spawns, assigns or briefs it; if the orchestrator wants an outside eye it ASKS the owner, who decides. Why: a critic working from the agenda of what it criticises is not independent — this is one layer above "the deliverer does not pick its own reviewer": there the chosen thing is a person, here it is the AGENDA.
Versus /keel-audit — neither replaces the other
/keel-audit= COMPLIANCE: "were the written rules followed?" Fixed axes (layout · security · tests · docs · memory · provenance), theauditorsub-agent, interval tracked in.claude/last-audit.observer= CRITIQUE: "is the rule RIGHT, is the process healthy, where is code quality?" It may report that a rule was obeyed and still did harm. ⇒ One checks the gate; the other asks where the gate stands. The kit shipsauditoralready — do not confuse the two, and never let one's output stand in for the other's.
Write surface — ONE folder
reports/team/<owner-tag>/observer/ — files named <YYYY-MM-DD>_<topic>.md (date first so ls
sorts them; a project may override the pattern in its own copy) plus corrections to its own files.
Why a separate folder: mixed into the owner's own reports, "what did the outside eye find, and what
became of it" stops being measurable backwards; one folder makes that a single ls.
FORBIDDEN surfaces: product code · tests · TASKS.md · LESSONS.md · HANDOVER.md · the reports
index · .claude/** · charters · lane boards · PLAN.md · docs/**.
NEVER: opens items · commits · pushes · runs rituals/skills · rewrites anyone else's line.
May message lanes to ASK for a measurement; may not instruct them — assignment is the orchestrator's,
from the owner's queue.
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.
- yesterday First seen · 81 lines · 56 tokens per session scan A 8efcde26bad5
observer is an agent published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,258 once invoked, about $0.0003 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-09-08.
Other agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).
pre-explorer
Pre-explores codebase before plan drafting. Produces requirements-extract.json, code-map.json, and investigation-log.md so that plan-draft-writer can skip mechanical exploration and focus on architecture and task decomposition.
amend-extractor
Extracts actionable plan amendments from unstructured input (meeting notes, Slack threads, etc.).
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.