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 kenshikobayashi/everything-claude-code-for-business --skill weekly-reportgit clone --depth 1 https://github.com/kenshikobayashi/everything-claude-code-for-businessWrote 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/kenshikobayashi/everything-claude-code-for-business/weekly-report)<a href="https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/weekly-report"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/weekly-report/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/kenshikobayashi/everything-claude-code-for-business/weekly-report"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/weekly-report.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.00017 | $0.00431 |
| Opus 5 | $0.00009 | $0.00216 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
weekly-report 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 12d 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 executing the /weekly-report command. Generate a comprehensive weekly status report.
Input
$ARGUMENTS — optionally with:
--team: Include team-level details--project [name]: Focus on specific project--period [YYYY-MM-DD]: Specific week (default: current week)
Steps
- Gather data for the week:
- Calendar: meetings attended, key decisions
- Tasks: completed, in-progress, blocked
- Email/Slack: key communications and outcomes
- Projects: milestone progress
- Structure as a weekly report
- Highlight wins and flag concerns
Output Format
## Weekly Report: [Period]
**Author**: [Name] | **Team**: [Team]
### This Week's Highlights
- 🎯 [Key achievement with impact]
- 🎯 [Key achievement]
### Completed
- [x] [Task/deliverable] — Impact: [what it enabled]
- [x] [Task/deliverable]
### In Progress
| Item | Progress | ETA | Risk |
|------|----------|-----|------|
| [Item] | 70% | MM-DD | 🟢 On track |
### Blockers & Risks
- 🔴 [Blocker] — Mitigation: [plan]
- 🟡 [Risk] — Watching: [indicator]
### Key Meetings & Decisions
- [Meeting]: Decided [what]. Next step: [action]
### Metrics (if applicable)
| Metric | Last Week | This Week | Trend |
|--------|-----------|-----------|-------|
### Next Week Plan
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
Constraints
- Focus on outcomes, not activities
- Include metrics where available
- Be honest about blockers
- Next week plan should be realistic (5-7 items)
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.
- 12d ago First seen · 65 lines · 17 tokens per session scan A 9886c9f0fd44
weekly-report is a skill published in the GitHub repository kenshikobayashi/everything-claude-code-for-business (2 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 431 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.