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 qte77/claude-code-plugins --skill synthesizing-cc-bigpicturegit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/synthesizing-cc-bigpicture)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/synthesizing-cc-bigpicture"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/synthesizing-cc-bigpicture.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.1 | $0.00000 | $0.01371 |
| Opus 5 | $0.00000 | $0.00685 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
synthesizing-cc-bigpicture 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Big-Picture Synthesis
Target: $ARGUMENTS
Synthesizes a plan to plan — an overarching view across all Claude Code artifacts. A reasoning tool that connects sessions, plans, tasks, and memories into a coherent narrative of what you're working on, why, and where you're headed.
Arguments
| Position | Name | Required | Default | Description |
|---|---|---|---|---|
| 1 | project-name |
no | all projects | Filter to a single project (substring, case-insensitive). Use all for all. |
| 2 | time-range |
no | all time | E.g. 7d, 30d, this-week. |
| 3 | output-path |
no | auto | Where to write output. |
Default output path:
project-nameset:<decoded-project-path>/docs/bigpicture.mdallor omitted:~/.claude/bigpicture.md- Explicit
output-path: overrides both.
Project matching: Matched against decoded ~/.claude/projects/<encoded-path>/
directories (- → / in encoding). Substring match on any path segment.
Examples:
/synthesizing-cc-bigpicture # All → ~/.claude/bigpicture.md
/synthesizing-cc-bigpicture Agents-eval # Single → project docs/
/synthesizing-cc-bigpicture Agents-eval 7d # Single, last 7 days
/synthesizing-cc-bigpicture all 30d ./bigpicture.md # All, 30 days, custom path
When to Use
- Starting a work session — orient across projects
- Planning what to work on next — strategic prioritization
- Sprint/week boundary — maintain the meta-plan
- Feeling stuck — surface current reasoning mode and whether a shift is needed
Do Not Use
- Searching a specific past conversation (use
/resumeor/history) - Per-session context (session-memory does this automatically)
- Real-time usage monitoring (use
/insights)
Project Filtering
When project-name is set (not all), ALL data collection and output must
respect the filter. Apply these rules once, consistently:
- Session allowlist: From
history.jsonl, collectsessionIdvalues whoseprojectfield matches (case-insensitive). - Project dirs: Filter
~/.claude/projects/*/to matching decoded paths. - Plans: Content-based — include only plans mentioning the project name.
- Tasks: Match task dir names against session allowlist (UUIDs) or filtered team names.
- Teams: Include only teams whose
config.jsonreferences the project name. - Session .jsonl: Only read files whose UUID is in the session allowlist.
- Output: Every section scoped to filtered data only. Exception: "Cross-Project Connections" may reference other projects as outbound links.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 129 lines · 0 tokens per session scan A 7464ee3fbb98
synthesizing-cc-bigpicture is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,371 tokens. 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
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
job-stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
wwas
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.