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 pantheon-org/tekhne --skill journal-entry-creatorgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/journal-entry-creator)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/journal-entry-creator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/journal-entry-creator/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/pantheon-org/tekhne/journal-entry-creator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/journal-entry-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 379 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Excessive Agency · line 290 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 366 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 369 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00123 | $0.05121 |
| Opus 5 | $0.00062 | $0.02560 |
| Sonnet 5 | $0.00025 | $0.01024 |
| Haiku 4.5 | $0.00012 | $0.00512 |
Grade A, and why
journal-entry-creator 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 8d 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 — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Entry Creator
Automate creation of structured journal entries with template schemas, frontmatter validation, and compliance checking.
Mindset
Every entry is a durable, queryable record, not a scratch note: get the frontmatter, triple-synced dates, and structure right the first time so future search and tooling can rely on them. Know when not to use this skill: a throwaway note with no frontmatter needs no ceremony.
Prerequisites
This skill is a companion to the journal CLI and is normally installed by it
(pantheon-journal skill install). Its features split into two tiers:
- Self-contained (no binary needed): interactive gathering, entry-type
selection, entry authoring, and structural validation via the bundled
scripts/validate-journal-entry.sh. - CLI-backed (require the
journalbinary onPATH): corpus-wide tag lint (pantheon-journal lint) and any otherpantheon-journalsubcommand this skill references.
Before running any journal ... command, confirm the binary is present:
pantheon-journal --version
If it is missing, the skill was installed without its companion CLI. Install the
journal CLI (its release binary, or cargo install), then retry. Until then,
skip the CLI-backed steps; the self-contained workflow still applies.
When to Use This Skill
Use journal-entry-creator when:
- Documentation requirement: User explicitly asks to "create journal entry", "document this", or "write about [topic]"
- Structured output needed: Standard journal workflows require YAML frontmatter, triple-sync dates, and template compliance
- Multiple entry types: Need to select between troubleshooting, learning, article summary, or general journal
- Validation critical: Entry must pass compliance checks before commit (automated validation available)
Do NOT use for:
- Quick markdown notes without frontmatter (use simple file creation instead)
- External documentation systems (Confluence, Notion) — this skill is for local .md files only
- Retrospective backfilling of frontmatter across many old entries: use
pantheon-journal backfillfor that one-pass batch repair instead
What ships with it
30 files 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.
- .audits/2026-02-24/analysis.md 5.3 KB
- .audits/2026-02-24/audit.json 147 B
- .audits/2026-03-02/analysis.md 1.1 KB
- .audits/2026-03-02/audit.json 416 B
- .audits/2026-03-02/remediation-plan.md 2.8 KB
- .audits/2026-03-03/analysis.md 1.0 KB
- .audits/2026-03-03/audit.json 417 B
- .audits/2026-03-03/remediation-plan.md 2.6 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 748 B
- assets/schemas/taxonomy.schema.json 1.8 KB
- assets/taxonomy.default.json 375 B
- assets/templates/article-summary.yaml 11 KB
- assets/templates/journal-entry.yaml 9.8 KB
- assets/templates/learning.yaml 8.5 KB
- assets/templates/ticket-kickoff.yaml 16 KB
- assets/templates/ticket-refinement.yaml 12 KB
- assets/templates/troubleshooting.yaml 12 KB
- CHANGELOG.md 2.0 KB
- evals/scenario-01.md 3.9 KB
- evals/scenario-02.md 4.0 KB
- evals/scenario-03.md 5.1 KB
- evals/scenario-04.md 4.0 KB
- evals/scenario-05.md 4.4 KB
- references/compliance.md 9.0 KB
- references/edge-cases.md 3.9 KB
- references/example-journal-entry.md 8.8 KB
- references/example-with-frontmatter.md 20 KB
- references/journal-command.md 3.1 KB
- scripts/validate-journal-entry.sh 13 KB runs code
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.
- 8d ago First seen · 480 lines · 123 tokens per session scan A 2b0a564e55ab
journal-entry-creator is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 5,121 once invoked, about $0.0006 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
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…
officecli-academic-paper
Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper'…
officecli-data-dashboard
Use this skill to build a multi-element Excel dashboard — Dashboard sheet on open, multiple formula-driven KPI cards, multiple charts, sparklines, and conditional formatting — from CSV or tabular input. Trigger on: 'dashboard', 'KPI dashboard', 'analytics dashboard', 'executive dashboard', 'metrics dashboard', 'CSV to…
A set of instructions for working with PDF files, which are documents designed to preserve their layout across devices.
officecli
Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
mxl-decompile
A 1C tool that converts an existing tabular document layout (MXL) from Template.xml into a JSON layout definition. The JSON uses the same format accepted by the corresponding layout compiler.