Borrowing it
Nothing to install: this file belongs to sussdorff/timing-cli. 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/sussdorff/timing-cli/main/.agents/skills/cognovis-pr/SKILL.mdgit clone --depth 1 https://github.com/sussdorff/timing-cliWrote 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/sussdorff/timing-cli/cognovis-pr)<a href="https://agentmods.dev/skills/sussdorff/timing-cli/cognovis-pr"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/cognovis-pr/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/sussdorff/timing-cli/cognovis-pr"><img src="https://agentmods.dev/badge/skills/sussdorff/timing-cli/cognovis-pr.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.00043 | $0.00599 |
| Opus 5.5 | $0.00017 | $0.00240 |
| Sonnet 5.5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
cognovis-pr 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 24d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cognovis Pull Requests
Write one outcome-led pull request text that a reviewer can judge in a minute.
This skill produces text only. ccore pr ensure publishes it; the executive-pack
delivery owns the merge decision. The Forgejo
review channel is operated by forgejo-review-channel, not here.
Inputs
- Repository root, the delivered change, the work order or spec it answers.
- Verified evidence: commands run with verdicts, screenshots for a user-visible surface, and known residuals.
- From the delivery: the
finding_triage.py --review-decisionsoutput, the non-author verifier's verdict with the head SHA it verified, the model route each reviewer used, the product decision and economic damage assessments, and the Risk statement content when the review risk is notnone.
Outputs
- One Markdown file outside the worktree. Line one is the title, at most 120
characters; the sections follow in the order defined by
references/authoring.md.
Workflow
- Read the installed
prskill, project-local before global, and use its live template for the body.references/authoring.mdresolves it and holds only what Cognovis adds.pris installed globally on each host byharness bootstrap; the Library does not ship it, and a missing one is a setup failure to report. - Write the body from that template, then add the Cognovis sections defined in
references/authoring.md: the work-order reference, Review decisions, Verification, reviewer routes, Merge assessment, Risk statement and Known residuals. That reference is the only place this list is held; a caller supplies the content, not a second list. - Attach walkthrough evidence only when a user-visible surface changed, after the pull request exists, per the reference.
- Pass the file to
ccore pr ensureas its--summaryvalue. Do not add the identity footer; ccore appends harness, session and work-order identity.
Do NOT
- Print or commit secret values, prompts, customer data, or pilot identifiers.
- Commit screenshots or other binary evidence into the repository.
- Publish or merge from here, or create a second creation transport beside
ccore pr ensure.
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.
- 24d ago Changed · +7 lines · +7 tokens per session 1463ad23a3c2
- 1mo ago Changed · +2 tokens per session 1ce67fb54a02
- 1mo ago First seen · 52 lines · 34 tokens per session scan A dd0f9da952f0
cognovis-pr is a skill published in the GitHub repository sussdorff/timing-cli (1 stars, last pushed 10d ago), licensed MIT. It adds 43 tokens to every session and 599 once invoked, about $0.0002 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-09-24.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.