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.
git clone --depth 1 https://github.com/Lyzr-Cognis/claude-cognisWrote 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/commands/lyzr-cognis/claude-cognis/project-config)<a href="https://agentmods.dev/commands/lyzr-cognis/claude-cognis/project-config"><img src="https://agentmods.dev/badge/commands/lyzr-cognis/claude-cognis/project-config/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/commands/lyzr-cognis/claude-cognis/project-config"><img src="https://agentmods.dev/badge/commands/lyzr-cognis/claude-cognis/project-config.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.00024 | $0.00256 |
| Opus 5 | $0.00012 | $0.00128 |
| Sonnet 5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
project-config 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 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.
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.
What it actually says
Project Configuration
Update the per-project Cognis configuration stored at .claude/.cognis-claude/config.json.
Configurable Keys
apiKey— Lyzr API key for this project (overrides global/env)ownerId— Owner ID override for this projectagentId— Personal agent ID overriderepoAgentId— Team/repo agent ID overridesignalExtraction— Enable signal-based transcript filtering (boolean)signalKeywords— Keywords that trigger signal extraction (array of strings)
Instructions
- Ask the user which setting they want to configure.
- Read the current config from
.claude/.cognis-claude/config.json(if it exists). - Update the requested key(s).
- Write the updated config back to the file.
- Confirm the changes.
Example
To set the API key for this project:
{
"apiKey": "lyzr-your-api-key-here"
}
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 · 36 lines · 24 tokens per session scan A ae637aff79e5
project-config is a command published in the GitHub repository Lyzr-Cognis/claude-cognis (20 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 256 once invoked, about $0.0001 per session on Opus 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.