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 agentmods add commands/perniemann/pncore/pn-audit-datagit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-audit-data)<a href="https://agentmods.dev/commands/perniemann/pncore/pn-audit-data"><img src="https://agentmods.dev/badge/commands/perniemann/pncore/pn-audit-data.svg" alt="Measured on agentmods" 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.00042 | $0.00919 |
| Opus 5 | $0.00021 | $0.00460 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
pn-audit-data 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pn-audit-data
Start every response with: [pn-command] 🔺
Advanced (palette-hidden). Not in the
/slash palette. Invoked by the/pn-backend-auditumbrella, or directly viaget_command("pn-audit-data").
Focused data model pass: design or review database schema, indexing strategy, migration approach, and data integrity constraints. No API design changes (use pn-audit-api), no query optimization (use pn-audit-performance) — data model only.
Flow
1. Context
Check .pncore-stack.md for ORM, database type, and existing schema info. If not found, ask:
- "What database? (PostgreSQL / MySQL / SQLite / MongoDB / other)"
- "What ORM? (Prisma / Drizzle / Sequelize / SQLAlchemy / ActiveRecord / sqlx / none)"
- "Designing from scratch or reviewing existing schema?"
2. Scope
If reviewing existing: "Which tables or domains should I focus on? Or reply 'all' for full schema review." If designing: "Describe the domain in 2–3 sentences — what entities need to be stored and how do they relate?"
3. Audit or Design
Consult pn-core://skills/backend/reference/database-patterns.md and load get_skill("pn-database-migrations").
For reviewing existing schema:
Normalization:
- Tables beyond 20 columns? Candidate for splitting?
- Repeating groups of columns (
tag1,tag2,tag3)? → Normalize to junction table. - Denormalized fields that drift from source? → Document the sync strategy.
Constraints:
- Foreign keys declared as DB constraints (not just app-level)?
- NOT NULL defaults where appropriate?
- CHECK constraints for enum-like columns?
- Money stored as float? → Should be integer cents.
Indexing:
- Foreign key columns missing indexes?
- High-traffic WHERE columns missing indexes?
- Composite indexes for multi-column filter patterns?
- Unused indexes slowing writes? (Check
pg_stat_user_indexes)
Soft deletes:
deleted_atwithout partial index? → AddWHERE deleted_at IS NULLpartial index.- Queries missing
WHERE deleted_at IS NULL?
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.
- 5d ago First seen · 98 lines · 42 tokens per session scan A 885b022acbe0
pn-audit-data is a command published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 919 once invoked, about $0.0002 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-31.
Other commands, from other repositories
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
t800-start
Единая команда. Создание rules, skills, commands, subagents, hooks — для плагина, текущего проекта или глобально.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
t800-doctor
Зачем: быстрый scripts-only отчёт: версия, profile, memory, STATE, counts, alwaysApply, последние audits — без narrative-агента по умолчанию.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
t-800-factory-validate
Запусти проверки и при необходимости вызови аудитора.