agentmods.dev

cognigy-plugin: Command for Claude Code

.claude/commands/pr-template.md

pr-template is a command for Claude Code from Cognigy/cognigy-plugin. It costs 0 tokens per session (451 once invoked), scanned A, original, MIT.

A command that writes a pull request description by examining the commits and code changes on the current branch since it split from the main branch. A pull request is a request to review and merge those changes.

In plain words
What is it for?
Use it to prepare a copy-ready pull request summary, change table, affected API or component notes, and release or migration information.
Why use it?
It saves the developer from manually reconstructing what changed and helps surface affected components, breaking changes, and migration steps.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Cognigy/cognigy-plugin's own configuration. It tells Claude Code how to work on cognigy-plugin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cognigy-plugin configures →

not rated 18repo yesterday A scan 0 tokens original MIT
View source ↗ Cognigy/cognigy-plugin
Reuse

Borrowing it

Nothing to install: this file belongs to Cognigy/cognigy-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Cognigy/cognigy-plugin/main/.claude/commands/pr-template.md
Clone the repo
git clone --depth 1 https://github.com/Cognigy/cognigy-plugin

Made for: Claude Code.

Wrote 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.

agentmods badge for pr-template

README.md
[![agentmods](https://agentmods.dev/badge/commands/cognigy/cognigy-plugin/pr-template/github.svg)](https://agentmods.dev/commands/cognigy/cognigy-plugin/pr-template)
Your own site
<a href="https://agentmods.dev/commands/cognigy/cognigy-plugin/pr-template"><img src="https://agentmods.dev/badge/commands/cognigy/cognigy-plugin/pr-template/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.

agentmods 80×15 button for pr-template

Your own site · 80×15
<a href="https://agentmods.dev/commands/cognigy/cognigy-plugin/pr-template"><img src="https://agentmods.dev/badge/commands/cognigy/cognigy-plugin/pr-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 451 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00451
Opus 5.5 $0.00000 $0.00180
Sonnet 5.5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

Measured 2mo ago against content hash 7ae890ec47e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-template 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 2mo 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.

.claude/commands/pr-template.md · 46 lines

What it actually says

Generate a pull request description for the current branch by analyzing all commits and changes since diverging from main.

Steps

  1. Run these commands in parallel to gather context:

    • git log main..HEAD --oneline — list commits on this branch
    • git diff main...HEAD --stat — files changed summary
    • git diff main...HEAD — full diff for content analysis

  2. Analyze the changes and determine:

    • What type of change this is (feature, fix, refactor, docs, chore, release)
    • Which tools, APIs, or components are affected
    • Whether any breaking changes or migration steps are needed

  3. Output the PR description inside a single fenced code block (```md ... ```) so the user can copy-paste it directly. The content inside the code block must follow this template exactly:

## Summary

- <bullet summarizing the main change — lead with the verb: Add, Fix, Update, Remove, Refactor>
- <additional bullet if there are secondary changes>
- <optional: note any breaking changes or migration required>

## Changes

| File / Component      | Description            |
| --------------------- | ---------------------- |
| `<file or component>` | <what changed and why> |
| `<file or component>` | <what changed and why> |

## Test plan

Automated — CI runs tests and Prettier checks on every PR via `.github/workflows/pr.yml`.
  1. After the code block, suggest a PR title (under 70 characters) on its own line.

Guidelines

  • Use present tense imperative verbs: "Add", "Fix", "Update", "Remove"
  • The Summary section should answer "what and why", not "what files changed"
  • The Changes table is the "what files" detail layer — use a markdown table so it renders cleanly on GitHub
  • The Test plan section should reference the automated CI checks, not manual steps
  • If the diff is large, group related changes in the Changes table
  • Flag any changes that affect the marketplace submission requirements (LICENSE, manifest.json, README, tool annotations, privacy policy)
Changes

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.

  1. 2mo ago First seen · 46 lines · 0 tokens per session scan A 7ae890ec47e5

Subscribe to this mod's changes

pr-template is a command published in the GitHub repository Cognigy/cognigy-plugin (18 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 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.

Git and workflow
Related

pr-template compared with commands from other repositories

pr-template next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pr-templateCognigy/cognigy-pluginCommand18yesterdayMITA0Claude Code
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
repo-audittractorjuice/arc-kitCommand2.3k2d agononeA29Claude Code
propsmill/infrahub-mcpCommand10yesterdayApache-2.0A18Claude Code
codex-reviewoalders/kitchen-sinkCommand54d agoMITA41Claude Code