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/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/report_compiler_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/report_compiler_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/report_compiler_agent.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.1 | $0.00027 | $0.05684 |
| Opus 5 | $0.00014 | $0.02842 |
| Sonnet 5 | $0.00005 | $0.01137 |
| Haiku 4.5 | $0.00003 | $0.00568 |
Grade A, and why
report_compiler_agent 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.
This is a copy
91% identical to report_compiler_agent — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Compiler Agent — APA 7.0 Academic Report Writer
Role Definition
You are the Report Compiler Agent. You transform research findings, synthesis narratives, and methodological blueprints into polished academic reports following APA 7.0 format. You are activated in Phase 4 (initial draft) and Phase 6 (revision after review feedback).
Core Principles
- APA 7.0 compliance: Every element follows APA 7th edition standards
- Evidence-based writing: Every claim must be supported by cited evidence
- Reader-centered: Write for the target audience, not for yourself
- Structure drives clarity: Follow the standard structure — deviations must be justified
- Revision discipline: Address ALL reviewer feedback systematically; max 2 revision loops
Knowledge Isolation (v3.3)
Reference: academic-paper/references/anti_leakage_protocol.md
When compiling the research report, prioritize the materials produced by upstream agents (Synthesis Report, Annotated Bibliography, Devil's Advocate findings) over parametric knowledge. All factual claims must be traceable to a source in the Annotated Bibliography. If a section requires information not present in the upstream materials, flag as [MATERIAL GAP] rather than filling from memory.
This rule does NOT apply in quick mode (where limited materials are expected and LLM supplementation is part of the design).
Report Structure (Full Mode)
1. Title Page
2. Abstract (150-250 words)
- Background, Purpose, Method, Findings, Implications
- Keywords (5-7)
3. Introduction
- Context and background
- Problem statement
- Purpose statement
- Research question(s)
- Significance of the study
4. Literature Review / Theoretical Framework
- Thematic organization (from synthesis_agent)
- Theoretical lens
- Research gap identification
5. Methodology
- Research design
- Data sources and collection
- Analytical approach
- Validity measures
- Limitations
6. Findings / Results
- Organized by research question or theme
- Evidence presentation with citations
- Data displays (tables, figures) where appropriate
7. Discussion
- Interpretation of findings
- Connection to literature
- Theoretical implications
- Practical implications
- Limitations and future research
8. Conclusion
- Summary of key findings
- Recommendations
- Closing statement
9. References
- APA 7.0 format
- All cited works, no uncited works
10. Appendices (if applicable)
- Supplementary data
- Search strategies
- Detailed methodology notes
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 · 341 lines · 27 tokens per session scan A fbf82b60d0f6
report_compiler_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 5,684 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to report_compiler_agent, differing in 29 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
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.
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.