Borrowing it
Nothing to install: this file belongs to senda-labs/DQIII8. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/senda-labs/DQIII8/main/.claude/skills/weekly-review/SKILL.mdgit clone --depth 1 https://github.com/senda-labs/DQIII8Wrote 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/senda-labs/dqiii8/weekly-review)<a href="https://agentmods.dev/skills/senda-labs/dqiii8/weekly-review"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/weekly-review/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/senda-labs/dqiii8/weekly-review"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/weekly-review.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.00044 | $0.01195 |
| Opus 5 | $0.00022 | $0.00598 |
| Sonnet 5 | $0.00009 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
weekly-review 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/weekly-review — Weekly Dashboard Update
Trigger
User writes /weekly-review (typically on Mondays or Fridays).
The real project corpus is
my-projects/, notprojects/*.md.00_DASHBOARD.mdandsessions/are gitignored deliberately. This is a local-only artifact, no git push step, same convention as/handover.
Behavior
1. Read sessions from the last 7 days
sessions/ holds YYYY-MM-DD_session_N.md files written by /handover. Select
by filename date, not mtime — mtimes are churned by git operations and
backups, so they are not a reliable recency signal:
CUTOFF=$(date -d '7 days ago' +%Y-%m-%d)
ls /root/dqiii8/sessions/*.md \
| awk -v c="$CUTOFF" -F/ '{
d = substr($NF, 1, 10)
if (d ~ /^[0-9]{4}-[0-9]{2}-[0-9]{2}$/ && d >= c) print
}' \
| sort
The date-shape guard matters: sessions/ also holds a few legacy files that do
not start with a date (SESSION-20260529-netcup.md, pending_message_batch_api.md),
and a plain string comparison sorts those above any 2026-… name, pulling
them into every week. Note the original find … -newer <(date -d '7 days ago')
never worked at all — -newer compares against a file's mtime, and the
process-substitution FIFO is created now, so the predicate matched zero files on
every run.
Session notes have no YAML frontmatter. Each is a handover note with
# Session Handover — YYYY-MM-DD and ## sections (Operador,
Last 5 commits, Uncommitted changes, Tests, Active services,
Next steps). Extract the date from the heading and the first bullet of
## Next steps as the one-liner.
2. Read the status of all projects
The project corpus is my-projects/:
my-projects/PROJECT.md— the index. A markdown table with columnsProyecto | Estado | Descripción | Próximo paso, split across "Proyectos Activos" and "Proyectos en Diseño / Stalled" sections. This is the fastest source for the dashboard's status table.my-projects/<slug>/PROJECT.md— per-project detail. Status lives on a plain header line (Status: active | Stack: ...), not in YAML frontmatter.
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 · 125 lines · 44 tokens per session scan A 16d52e67619e
weekly-review is a skill published in the GitHub repository senda-labs/DQIII8 (11 stars, last pushed 23d ago), licensed MIT. It adds 44 tokens to every session and 1,195 once invoked, about $0.0002 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
using-adaptive-harness
Auto-mode bootstrap for adaptive-harness. Intercepts tasks, routes to optimal harness, evaluates results. Use on every task when adaptive-harness auto-mode is active.
task-taxonomy
Reference for the 6-axis task taxonomy used by adaptive-harness routing. Use when user asks how tasks are classified.
harness-registry
Manage the adaptive-harness pool: list, inspect, promote, demote harnesses. Use when user asks about harness status or wants to manage the pool.
skill-review-response
Use when a reviewer, CI bot, or another AI leaves feedback to address.
sys-configure
Configure Claude Octopus — redirects to /octo:setup interactive wizard.
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…