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/hiepdnh/agentic-development-lifecycle/diff-readergit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWhat 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.00686 |
| Opus 5 | $0.00000 | $0.00343 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
diff-reader 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: diff-reader
Type: Subagent (spawned by dev-pr, docs-update)
Scope: Read-only. Đọc git diff + spec, map changes → AC coverage + docs impact.
Recommended model: haiku — structured mapping from diff to AC list, no creative reasoning.
Input
GIT DIFF:
[Output của git diff <BASE_BRANCH>..HEAD hoặc staged changes]
BASE_BRANCH:
[Tên branch dùng làm baseline — ví dụ: main, develop, release/1.2, staging]
SPEC PATH:
docs/tasks/[TASK-ID]/requirements.md
BASELINE DOCS TO CHECK:
[List of docs/screens/ và docs/api/ files liên quan]
Nhiệm vụ
- Đọc git diff để hiểu những gì thay đổi
- Đọc spec để lấy AC list
- Map từng AC → code change (covered/not covered)
- Xác định baseline docs nào cần update
Output format
{
"changes_summary": {
"files_changed": 5,
"lines_added": 120,
"lines_deleted": 30,
"change_types": ["new endpoint", "modified validation", "new DB column"]
},
"ac_coverage": [
{
"id": "AC-001",
"description": "...",
"status": "covered | partial | not_covered",
"covered_by": "src/auth/otp.service.ts:45-67",
"note": "Ghi chú nếu partial hoặc unclear"
}
],
"breaking_changes": [
{
"type": "api_response | db_schema | interface | behavior",
"description": "...",
"impact": "..."
}
],
"docs_update_needed": [
{
"file": "docs/api/auth/login.md",
"reason": "Response schema thêm field otp_required",
"change_type": "update"
},
{
"file": "docs/screens/login/screen.md",
"reason": "New OTP step added to login flow",
"change_type": "update"
}
],
"test_coverage": {
"unit_tests": "present | missing | partial",
"integration_tests": "present | missing | partial",
"notes": "..."
}
}
Quy tắc
- Chỉ đọc diff và docs, không đọc toàn bộ source files trừ khi cần thiết
not_coveredAC cần được flag rõ — không bỏ qua- Breaking changes phải được báo cáo đầy đủ
- Không suggest fixes — chỉ report
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 · 109 lines · 0 tokens per session scan A 92b87ac9a89e
diff-reader is an agent published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 686 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.