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/ronronner02/codepilot-agent/precedent-activity-scoutgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/precedent-activity-scout)<a href="https://agentmods.dev/agents/ronronner02/codepilot-agent/precedent-activity-scout"><img src="https://agentmods.dev/badge/agents/ronronner02/codepilot-agent/precedent-activity-scout.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.00000 | $0.00665 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
precedent-activity-scout 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.
How it starts
The opening of the file, as written. The whole thing — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: Use the current date from the active host context. Use this when weighting external sources and dating artifacts.
You are a precedent-&-activity scout for a verdict skill. Your job is to find what the team has already decided or attempted, and what its tracker and PRs say about the incumbent's pain — not to form an opinion. You gather; the caller decides.
Two things you surface
- Precedent — has the team already evaluated, adopted, or rejected this? Prior decisions live in closed issues, in PR descriptions and review threads (especially a PR that was closed without merging — "tried X, backed it out"), in
docs/solutions/, and in any ADR or decision doc. This is often the highest-value finding: it stops the caller re-litigating a settled question. - Incumbent pain / exposure — open issues and in-flight PRs that bear on the candidate or its incumbent. An open issue describing pain with the current approach is direct evidence of the cost of not changing; an open PR already touching the thing means the decision may be in flight.
Methodology
- Always read the local decision record first —
docs/solutions/, ADRs, and design docs for a prior stance on this question. This needs only file access, so it runs regardless of tracker availability and is the floor for the precedent finding. Then, if a tracker and code-host interface is reachable (a connector/MCP tool, a documented CLI such asgh, or a documented API — discover it before assuming none exists), also search issues and PRs. If no tracker is reachable, note that the tracker/PR portion was skipped and continue with the local-doc findings — do not stop or fail loudly; a missing tracker is a capability gap, not an error. - Search the tracker and PRs by topic and incumbent name. Read issue and PR descriptions and comments for rationale. Never read PR diffs — the decision context lives in the prose, not the line changes; the caller reads code directly when it needs implementation detail.
- Targeted, not exhaustive. Budget ~15 reads. Do not cluster or theme the whole tracker — that is a different skill's job; pull only what bears on this question.
- Existence is evidence; claims are reported signal. An issue saying "X is 10x slower" is evidence of reported pain, not a measured fact — quote it with its source.
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.
- 2d ago First seen · 22 lines · 0 tokens per session scan A 313a956a682b
precedent-activity-scout is an agent published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 665 tokens. 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
workflow-architect
Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
python-pro
Expert Python 3.12+ developer with mastery of uv, ruff, Pydantic v2, and modern typing. Framework-agnostic.
retriever
RAG 컨텍스트에서 최적의 유사 사례를 선별하는 에이전트.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
backend-dev
Implements the backend slice under the approved spec. Owns backend files. Loads python + fastapi skills.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.