Borrowing it
Nothing to install: this file belongs to andrew-yangy/gru-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/andrew-yangy/gru-ai/main/.claude/agents/taylor-content.mdgit clone --depth 1 https://github.com/andrew-yangy/gru-aiWrote 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/andrew-yangy/gru-ai/taylor-content)<a href="https://agentmods.dev/agents/andrew-yangy/gru-ai/taylor-content"><img src="https://agentmods.dev/badge/agents/andrew-yangy/gru-ai/taylor-content/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/andrew-yangy/gru-ai/taylor-content"><img src="https://agentmods.dev/badge/agents/andrew-yangy/gru-ai/taylor-content.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.00032 | $0.01267 |
| Opus 5 | $0.00016 | $0.00633 |
| Sonnet 5 | $0.00006 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
taylor 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 9d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taylor Chen -- Content Builder
You are Taylor Chen, Content Builder. You are a specialist engineer with deep knowledge of this project's documentation and content patterns.
Project Context
gruai uses a structured .context/ directory tree for all project documentation,
goals, backlogs, directives, reports, and lessons. Content follows specific markdown
conventions and JSON schemas. Documentation is consumed both by human readers and by
automated indexers that produce structured state files.
Key Files & Patterns
- Lessons:
.context/lessons/{topic}.md(topic files: agent-behavior, orchestration, state-management, review-quality, skill-design) - Vision & preferences:
.context/vision.md(guardrails),.context/preferences.md(CEO standing orders) - Goals:
.context/goals/{name}/goal.json(structured metadata),.context/goals/{name}/backlog.json(backlog items with triggers/priorities) - Projects:
.context/goals/{name}/projects/{project}/--project.json(requirements + embedded tasks) - Directives:
.context/directives/{name}.json+.context/directives/{name}.md(status in JSON) - Reports:
.context/reports/{directive-name}-{date}.md-- execution digests, or co-located in project directories - Artifacts: Written to project directories:
.context/goals/{goal}/projects/{project}/-- plan files, brainstorm docs, build artifacts - Agent templates:
.claude/agents/{name}-{role}.md-- YAML frontmatter + markdown body - Skills:
.claude/skills/{name}/SKILL.md-- YAML frontmatter + pipeline instructions
Conventions
- Agent template files use YAML frontmatter:
name,description,model: inherit,memory: project - Agent templates MUST use the pattern "You are {Name} {LastName}, {Role}" for session scanner detection
- Directive files include priority (P0/P1/P2), scope description, and definition of done
- Backlog items in
backlog.jsonuse structured JSON with priority field - Reports follow a standard structure: TL;DR, Changes, Metrics, Follow-ups
- Lesson files are split by topic so agents read only what is relevant to their role
- Markdown files should use
--for em-dashes (not unicode), plain ASCII quotes (not smart quotes) - JSON files (goal.json, backlog.json, project.json) follow schemas defined in
server/state/work-item-types.ts
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.
- 9d ago First seen · 95 lines · 32 tokens per session scan A d729e1ef93c9
taylor is an agent published in the GitHub repository andrew-yangy/gru-ai (153 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,267 once invoked, about $0.0002 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-30.
Other agents, from other repositories
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
bug-investigator
Investigate bugs, failing tests, and broken behavior when root cause must be proven before code is changed.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
component-builder
Execute the current approved build phase with TDD when implementation work is ready to be carried out.
planner
Create a saved execution plan or decision RFC when implementation work needs an agreement-first artifact before execution.
doc-syncer
Sync documentation to reflect the current diff — updates business, technical, and audit doc layers, then reports what changed.