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 commands/egorus1/ask-a-senior/loggit clone --depth 1 https://github.com/egorus1/ask-a-seniorWrote 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/commands/egorus1/ask-a-senior/log)<a href="https://agentmods.dev/commands/egorus1/ask-a-senior/log"><img src="https://agentmods.dev/badge/commands/egorus1/ask-a-senior/log.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.00009 | $0.00108 |
| Opus 5 | $0.00005 | $0.00054 |
| Sonnet 5 | $0.00002 | $0.00022 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
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 4d 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
Read .ask-a-senior/log.md in the project root and show it.
If the file doesn't exist yet, say so in one line — nothing has resolved yet.
Show the entries as they are. Don't summarise them, don't score them, and don't comment on their quality. It's their record, not a report card. If they ask what it's for: it's the list of things they now actually own.
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.
- 4d ago First seen · 13 lines · 9 tokens per session scan A b6c15fcc7e31
log is a command published in the GitHub repository egorus1/ask-a-senior (2 stars, last pushed 14d ago), licensed MIT. It adds 9 tokens to every session and 108 once invoked, about $0.0000 per session on Opus 5. 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 commands, from other repositories
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
save
Save this conversation as a new or existing reusable context.
launch-meta-campaign
Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.
import
Import a shared context bundle, or take a teammate's newer copy of one you already have.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
create-topic
Research and generate a complete topic plan with keyword mapping, audience, angle, and competitive positioning.