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 Cody-W-Tucker/Cognitive-Assistant --skill project-dashboardgit clone --depth 1 https://github.com/Cody-W-Tucker/Cognitive-AssistantWrote 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/cody-w-tucker/cognitive-assistant/project-dashboard)<a href="https://agentmods.dev/skills/cody-w-tucker/cognitive-assistant/project-dashboard"><img src="https://agentmods.dev/badge/skills/cody-w-tucker/cognitive-assistant/project-dashboard/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/cody-w-tucker/cognitive-assistant/project-dashboard"><img src="https://agentmods.dev/badge/skills/cody-w-tucker/cognitive-assistant/project-dashboard.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.01314 |
| Opus 5 | $0.00022 | $0.00657 |
| Sonnet 5 | $0.00009 | $0.00263 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
project-dashboard scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
2. **Gather git data**: `subprocess.run` for each repo, capture stdout, handle timeouts How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
When the user needs a bird's-eye view across all active projects — which ones have momentum, which are stalled, which have uncommitted work at risk, and which client deals need attention. Triggers on requests like "project status overview," "what's active right now," "dashboard for all my repos," "track blockers across projects," or "set up automated project tracking."
Architecture
Dashboard File
A single markdown file (typically at the project root, e.g. /data/projects/DASHBOARD.md) with three zones:
- Auto-generated sections wrapped in
<!-- AUTO-START:NAME -->/<!-- AUTO-END:NAME -->markers. These are machine-regenerated on each refresh. Separate markers per data source (e.g.PROJECTS,DEALS). - Manual notes section — hand-maintained by the user for blockers, context, and decisions. Lives outside the markers.
- Timestamp line at the top showing last refresh time and cadence.
The update script replaces ONLY content between markers using regex (re.DOTALL). Manual notes outside markers survive every refresh.
Git Activity Classification
Scan all git repos under the projects root (max depth 3 for nested/submodule repos). For each repo, run:
git log -1 --format='%ci %s' → last commit
git log --since='7 days ago' --oneline → count
git log --since='30 days ago' --oneline → count
git status --porcelain → uncommitted count
Classification rules:
| Class | Rule | Emoji |
|---|---|---|
| Active | ≥1 commit in last 7 days | 🔴 |
| Semi-Active | ≥1 commit in last 30 days, none in 7 | 🟡 |
| Dormant | No commits in 30+ days | ⚫ |
Also surface uncommitted files as a risk signal (work that could be lost).
CRM Integration
Pull deal status from the CRM SQLite database. Active deals: stage NOT IN (closed-won, closed-lost). Recently closed: last 6 months. Map deals to repos where a corresponding project directory exists.
CRM schema notes (SQLite with JSON columns):
deals.contacts— JSON array of contact IDs,json_extract(d.contacts, '$[0]')for primarydeals.stage— values includequalified,closed-won,closed-lost- Deals link to contacts via JSON arrays, contacts link to companies
What ships with it
1 file 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.
- 12d ago First seen · 110 lines · 44 tokens per session scan A 946fc8bbb566
project-dashboard is a skill published in the GitHub repository Cody-W-Tucker/Cognitive-Assistant (11 stars, last pushed 25d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,314 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.