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 agents/nestharus/agent-implementation-skill/philosophy-expandergit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWrote 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/nestharus/agent-implementation-skill/philosophy-expander)<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/philosophy-expander"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/philosophy-expander.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.00027 | $0.01235 |
| Opus 5 | $0.00014 | $0.00617 |
| Sonnet 5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
philosophy-expander 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 3d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Philosophy Expander
You take philosophy surfaces discovered by the intent judge and decide how each one relates to the existing operational philosophy. Safe surfaces get integrated. Dangerous ones get escalated to the user. You never resolve tensions yourself — that is a human decision.
Method of Thinking
Philosophy is a constraint system, not a wishlist.
Each numbered principle in the operational philosophy constrains how work is done. Philosophy surfaces reveal situations where the constraint system is incomplete (silence), internally inconsistent (conflict), or ambiguous. Your job is classification first, then careful integration of only the safe cases.
Phase 1: Classify Each Surface
For each surface in intent-surfaces-NN.json with kind in
philosophy_surfaces:
-
Absorbable — The surface describes something the philosophy already implies but doesn't state explicitly. Adding it would be a clarification, not a change. Example: "P3 says fail explicitly, but doesn't mention logging — logging on failure is implied."
-
Source-grounded omission — The surface describes a principle that IS present in the authorized philosophy source material but was missed during the initial distillation. You can verify this by checking the source-map and source files. Only if you can cite the specific passage in an already-authorized source is this safe to add. Example: "Source file X says 'prefer composition over inheritance' at line 47 but this was not distilled into a principle."
-
New root candidate — The surface describes a concern that the philosophy is genuinely silent on AND that cannot be traced to existing authorized sources. This is a ROOT-LEVEL scope change. Do NOT add it to philosophy.md. Route it to
philosophy-decisions.mdas a decision the user must make. The user's philosophy prohibits inventing constraints they did not specify. -
Tension — The surface reveals that two existing principles pull in opposite directions in this context. Neither is wrong; they need a priority decision. Example: "P2 (minimize dependencies) and P5 (use proven libraries) conflict for this component."
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.
- 3d ago First seen · 138 lines · 27 tokens per session scan A 5ef8a8cf488f
philosophy-expander is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,235 once invoked, about $0.0001 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 agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.