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 pjt222/agent-almanac --skill conscientiousnessgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/conscientiousness)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/conscientiousness"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/conscientiousness.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.01596 |
| Opus 5 | $0.00054 | $0.00798 |
| Sonnet 5 | $0.00022 | $0.00319 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade A, and why
conscientiousness 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conscientiousness
Systematic thoroughness and diligence — ensuring completeness, verifying results, following through on every commitment, and finishing tasks to the standard they deserve.
When to Use
- Before marking a task as complete — as a final verification pass
- When a response feels "good enough" but the task deserves better
- After a complex multi-step operation where individual steps may have drifted
- When the user's request has multiple parts and each part needs verification
- Before submitting code, documentation, or any deliverable for user review
- When self-monitoring detects a pattern of cutting corners or rushing
Inputs
- Required: The task or deliverable to verify (available from conversation context)
- Optional: The original user request (for comparison against what was delivered)
- Optional: Any checklist or acceptance criteria provided by the user
- Optional: Prior commitments made during the session (things promised but not yet checked)
Procedure
Step 1: Reconstruct the Full Commitment
Before checking work, re-establish exactly what was committed to.
- Re-read the user's original request carefully — not the interpreted version, the actual words
- List every explicit requirement mentioned
- List every implicit commitment made during the session:
- "I'll also update the tests" — was this done?
- "Let me fix that too" — was this completed?
- "I'll check for edge cases" — were they checked?
- Note any acceptance criteria the user provided
- Compare the commitment list against what was actually delivered
Got: A complete list of commitments — explicit requirements plus implicit promises — with a preliminary match against deliverables.
If fail: If the original request is no longer in context (compressed), reconstruct from what remains and acknowledge any gaps to the user.
Step 2: Verify Completeness
Check that every committed item was addressed.
Completeness Matrix:
+---------------------+------------------+------------------+
| Commitment | Status | Evidence |
+---------------------+------------------+------------------+
| [Requirement 1] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
| [Requirement 2] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
| [Promise 1] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
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 First seen · 154 lines · 108 tokens per session scan A 30f26aa8e676
conscientiousness is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 1,596 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
implementation-discovery
Internal contract: the single owner of the bounded pre-write implementation discovery step. One read-only mapper that closes seven evidence questions, emits one fixed compact map, and routes READY | REPLAN | NEEDS-DESIGN | BLOCKED before any branch, planning, or source write. Consumed only by execute-phase on the…
crisis-holding
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
voice-extractor
Capture a user's real writing voice from 5-20 prior samples, store a local voice.yaml fingerprint, and enforce it on newsjack drafts so AI tells disappear. Measures voice with named stylometry lenses (Burrows's Delta function-word vector, MATTR lexical diversity, sentence-length burstiness, Biber Dimension-1 register…
fact-check
Extract factual claims from PR copy, verify each claim independently, attach concrete citations, and warn when certainty is low. Runs each claim through proven newsroom verification methods (lateral reading, source-tier climbing, provenance pillars, triangulation, calibrated rating) and puts the burden of proof on the…
eval-graphics
Turn an eval study's numbers into on-brand, publish-ready figures using the Newsjack chart room (the eval design system), then validate them with Playwright. For producing the charts in a published eval/data study.
coverage-tracker-setup
Set up a lightweight Google Alerts-style coverage tracker for any number of keywords. Creates a tracker config with each keyword and what it actually means, then hands recurrence to the user's agent harness.