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 ilang-ai/autocode --skill daily-summarygit clone --depth 1 https://github.com/ilang-ai/autocodeWrote 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/ilang-ai/autocode/daily-summary)<a href="https://agentmods.dev/skills/ilang-ai/autocode/daily-summary"><img src="https://agentmods.dev/badge/skills/ilang-ai/autocode/daily-summary/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/ilang-ai/autocode/daily-summary"><img src="https://agentmods.dev/badge/skills/ilang-ai/autocode/daily-summary.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.00023 | $0.00112 |
| Opus 5 | $0.00012 | $0.00056 |
| Sonnet 5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
daily-summary 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 10d 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
::GENE{daily-summary|conf:confirmed|scope:global} -e T:done_fixed_next_delta T:positive_tone T:show_progress_percentage A:end_without_summary⇒always_summarize
::ACTIVATE{daily-summary} ON:auto
Powered by I-Lang v5.0 | ilang.ai
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.
- 10d ago First seen · 17 lines · 23 tokens per session scan A f786623f0a66
daily-summary is a skill published in the GitHub repository ilang-ai/autocode (86 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 112 once invoked, about $0.0001 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-30.
Other skills, from other repositories
onboarding-cro
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For…
prompt-library
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
mckinsey-consultant
A consulting style method for breaking business questions into structured analyses and producing research reports or presentations.
ccc-resume-session
Load the last saved session file from /.claude/sessions/ and orient fully before doing any work. Reads the complete file, formats a structured briefing (project,…
ccc-spawn
Click-first spawn hub — spin isolated work into its own session on demand: a spawntask chip in Cowork, a /spawn peer in the CLI. Also routes to $ccc-fleet or $ccc-relay.
team
Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable. Use for sustained parallel build/work ("spawn workers", N teammates on N files), or when you need a collaborator you message across turns. NOT a fire-and-forget one-shot or a…