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 adam-s-k-i/super-backlog --skill project-profilegit clone --depth 1 https://github.com/adam-s-k-i/super-backlogWrote 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/adam-s-k-i/super-backlog/project-profile)<a href="https://agentmods.dev/skills/adam-s-k-i/super-backlog/project-profile"><img src="https://agentmods.dev/badge/skills/adam-s-k-i/super-backlog/project-profile/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/adam-s-k-i/super-backlog/project-profile"><img src="https://agentmods.dev/badge/skills/adam-s-k-i/super-backlog/project-profile.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.00065 | $0.00871 |
| Opus 5.5 | $0.00026 | $0.00348 |
| Sonnet 5.5 | $0.00013 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
project-profile 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Profile: name the critical areas of this project
Writes backlog/docs/critical-areas.md. The managed AGENTS.md block tells
every agent to read it at session start: everything it lists runs on the top
tier, and everything under "Independent check" is verified by a second
subagent before use. Guide:
https://adam-s-k-i.github.io/super-backlog/guide/project-profile.
When this skill runs
backlog/docs/critical-areas.mdis missing (offered once per block rule 8).- The user asks for it.
- The project changed substantially: new modules, new risks, going live.
- A misclassification caused a mistake.
- A provisional profile can now be judged better, or
sbl doctorreports it as provisional.
Procedure
- Tier check. Assessment and wording are top-tier work only. If the session
runs on a lower tier, hand both to a subagent on the top tier; fact
gathering (step 2) may go to Light or Standard. If no top-tier model is
available, write a draft, end the Status line with
provisional, and tell the user once that it should be revised with the strongest model. - Targeted overview, no full reading: project description, existing
instructions (AGENTS.md, CLAUDE.md), README, directory layout, central
modules, and
backlog/docs/architecture.ymlif present. - Guiding question: where would a mistake go unnoticed and be costly or hard to reverse? Check at least: money, law, security and credentials, data loss and other irreversible actions, external visibility, decision-relevant metrics, structural choices with long-term consequences.
- Look specifically for work that looks like routine but silently determines results; the general tier rule does not catch these cases.
- Name explicitly what may go to lower tiers.
- If the project is too empty to judge, derive the profile from the user's
description and mark it
provisional. - Write
backlog/docs/critical-areas.mdin this format, at most 150 words below the Status line, 4 to 7 items grouped by risk area (not by activity),Independent check:only when something is irreversible:
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.
- 4d ago Changed 5b58c89bd1d0
- 5d ago First seen · 81 lines · 65 tokens per session scan A 43a1fa4691a4
project-profile is a skill published in the GitHub repository adam-s-k-i/super-backlog (2 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 871 once invoked, about $0.0003 per session on Opus 5.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-10-11.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
lens-dashboard
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this…
prism-dashboard
Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".
delegate
Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.
subagent-driven-delegation
Execute an implementation plan with the Superpowers subagent-driven-development loop while every task is implemented by a verified Claude Architect Producer — isolated worktree, frozen Candidate Artifact, independent verification, fresh-context review, runtime-gated acceptance. Use when executing a multi-task plan…
fleet-doctrine
Fleet Deck doctrine — how to behave as one Claude Code session among many on this machine. Use when you see [FLEETDECK] messages in context, when told to coordinate with / message / answer another session, when asked about the fleet board, or when deputized to decide something for another session.