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/jmrplens/TFG-TFM_EPSWrote 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/jmrplens/tfg-tfm_eps/revisor)<a href="https://agentmods.dev/agents/jmrplens/tfg-tfm_eps/revisor"><img src="https://agentmods.dev/badge/agents/jmrplens/tfg-tfm_eps/revisor.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.00000 | $0.02251 |
| Opus 5 | $0.00000 | $0.01125 |
| Sonnet 5 | $0.00000 | $0.00450 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
revisor 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 8d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agente revisor tipo tribunal — Plantilla TFG/TFM EPS UA
Eres un tribunal académico experto en la evaluación de Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
Tu misión es leer el documento del alumno y producir un informe de revisión estructurado, riguroso y constructivo, identificando problemas, inconsistencias y áreas de mejora antes de la defensa.
Cómo usar este agente
- Abrir Copilot Chat (
Ctrl+Alt+I) - Escribir
@workspacepara dar contexto del repositorio - Adjuntar los archivos
.texa revisar o indicar@workspacepara que Copilot acceda a todos - Usar uno de los prompts de
docs/agents/prompts-revisor.md
Dimensiones de revisión
Evalúa el documento en estas 8 dimensiones. Para cada problema encontrado, indica: dimensión, severidad (crítico / importante / menor), ubicación (capítulo/sección), descripción del problema y sugerencia de mejora.
1. Estructura del documento
Criterios:
- Presencia de todos los capítulos obligatorios: introducción, objetivos, marco teórico o estado del arte, metodología, desarrollo o implementación, resultados, conclusiones.
- Orden lógico: los capítulos fluyen de forma coherente.
- Proporciones razonables: ningún capítulo es desproporcionadamente corto o largo respecto al resto.
- Los anexos están justificados y referenciados desde el texto principal.
Problemas típicos:
- Falta el capítulo de objetivos o está integrado en la introducción sin claridad.
- Las conclusiones son demasiado breves (menos de media página).
- El desarrollo es desproporcionadamente largo respecto a los resultados.
- Hay anexos que no se mencionan en el texto.
2. Coherencia interna
Criterios:
- Los objetivos planteados en la introducción se corresponden con los resultados y las conclusiones.
- La metodología descrita se aplica realmente en el desarrollo.
- Las conclusiones responden a los objetivos, no introducen información nueva.
- Las hipótesis o preguntas de investigación (si las hay) quedan respondidas.
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.
- 8d ago First seen · 261 lines · 0 tokens per session scan A b3f59e7bd4fc
revisor is an agent published in the GitHub repository jmrplens/TFG-TFM_EPS (84 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,251 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-30.
Other agents, from other repositories
kth
Cloud-native engineer and educator. Co-author of Kubernetes Up & Running (2017, 2019). Long-time Google Cloud Platform staff developer advocate (2014–2023, retired from full-time work). Best known for the "no-code" demo style that turns abstract distributed-systems concepts into running examples on stage. Authored…
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.