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 skills add conectlens/lenserfight --skill async-standup-generatorgit clone --depth 1 https://github.com/conectlens/lenserfightWrote 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/skills/conectlens/lenserfight/async-standup-generator)<a href="https://agentmods.dev/skills/conectlens/lenserfight/async-standup-generator"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/async-standup-generator/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/skills/conectlens/lenserfight/async-standup-generator"><img src="https://agentmods.dev/badge/skills/conectlens/lenserfight/async-standup-generator.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.00029 | $0.00201 |
| Opus 5.5 | $0.00012 | $0.00080 |
| Sonnet 5.5 | $0.00006 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
async-standup-generator 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
Async Standup Generator
You are the Async Standup Generator Lens (Chainabit). Yesterday: [[yesterday]]. Today's plan: [[today]].
Rules:
- Lead with the one thing that changed for the team — not a personal task log.
- Call out one explicit blocker with the unblock owner.
- Flag any deliverable at risk of slipping with a concrete next checkpoint.
- End with one short question that invites a colleague to weigh in.
Keep it under 120 words. No emoji unless the user already used one.
Why this exists
Async standups become diary entries. This lens forces the standup to surface team-relevant signal and ends with an invite question, which is the only thing that turns broadcast into conversation.
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 · 22 lines · 29 tokens per session scan A b821d45fcdea
async-standup-generator is a skill published in the GitHub repository conectlens/lenserfight (18 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 201 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
request-progress
Group recent conversations into overall requests, review each one's progress from memory, link each to the owner goals it serves, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review…
potpie-source-ingestion
Use when the user explicitly asks to ingest, refresh, or deeply understand a repository, PR, issue, ticket, runbook, incident report, document, or web link into Potpie. The harness performs todo-driven discovery, uses local/GitHub/integration tools and read-only subagents when available, builds evidence-backed…
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
03_task5
Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.
screenpipe-worklog
Reconstruct a daily or weekly worklog from observed activity and outcomes.