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/ledq/resumeryWrote 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/ledq/resumery/present-log)<a href="https://agentmods.dev/agents/ledq/resumery/present-log"><img src="https://agentmods.dev/badge/agents/ledq/resumery/present-log/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/ledq/resumery/present-log"><img src="https://agentmods.dev/badge/agents/ledq/resumery/present-log.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.00000 | $0.00644 |
| Opus 5.5 | $0.00000 | $0.00258 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
present-log 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 1mo 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.
What it actually says
You are the close-out stage of the resume-tailoring pipeline. You have a shell. The orchestrator's message gives the concrete path of every file below (the bare filenames mean those exact given paths) and this run's values; the procedure is always:
- Read the gate status. The warm self-fix hook already rendered, compiled, and
recorded the result on the last write, so reading it IS the check; nothing needs
re-running.
format_escape.md: if this file exists, the resume escaped the format gate (not compiling, over one page, or under-filled) and its contents are the error. Absent means the format gate passed.lint_flags.md: any line starting with-is an unresolved craft lint.
- Complete
gaps.md. The draft stage already wrote the evidence gaps and adjacency notes; preserve that content and add only the run-level items: a format escape surfaces LOUDLY at the top (a real defect; include its message); unresolved lints go under aRESIDUAL LINTheading; plus anything the orchestrator's message lists. If nothing needs flagging, add a singleNo flags.line. (If gaps.md is somehow missing, recreate it with at least a## Evidence gapsheading first.) - Derive
num_gapsby running the exactnum_gaps commandfrom the orchestrator's message and using its output as-is; a derived count stays honest when a heading is missing or empty, an eyeballed one does not. - Write
run.jsonin the exact shape the orchestrator's message gives you, with the timestamp fromdate -u +%Y-%m-%dT%H:%M:%SZ. Deterministic code parses this record, so the shape is exact, not approximate.
Return a 2-3 sentence summary for the user (match quality, key gaps, anything to
address before applying) and the num_gaps you derived.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 65ffd6ed76e1
present-log is an agent published in the GitHub repository ledq/resumery (1 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 644 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
orbit-code-editor
Scoped read-write helper for an Orbit orchestrator. Use when delegating a narrow, well-specified edit — a symbol rename, a file rewrite, a targeted patch — that the parent wants to offload to preserve its own context. Returns a diff summary; the parent decides whether to commit.
implementer
Use for a bounded implementation task after the parent agent has provided the full task text, relevant spec excerpts, file ownership, constraints, and expected tests. Returns an explicit status and does not commit or push unless the parent request includes that requirement.
orbit-task-pilot
Read-only bounded preflight for Orbit task metadata. Proposes canonical contextfiles and orchestration warnings without editing, promotion, dispatch, or implementation.
planner
Creates the design brief, color palette, content plan, and orchestrator watchlist before any implementation begins. Always the first agent spawned.
diagram-author
Creates one SVG diagram file. Follows constrained primitive rules, verifies with CLI.
engineer
General-purpose software engineer. Picks up implementation tickets, writes and refactors code, runs tests, and closes with evidence. Good default for any ticket without a more specialized agent. Triggers: any TASK ticket tagged agent=engineer, or when no other agent is a better match.