Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pantheon-org/tekhnenpx agentmods add skills/pantheon-org/tekhne/journal-entry-importWrote 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-import)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/journal-entry-import"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/journal-entry-import/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-import"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/journal-entry-import.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Privilege Escalation · line 193 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 159 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 160 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.00161 | $0.02997 |
| Opus 5 | $0.00081 | $0.01499 |
| Sonnet 5 | $0.00032 | $0.00599 |
| Haiku 4.5 | $0.00016 | $0.00300 |
Grade A, and why
journal-entry-import 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 6d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Entry Import
Reconstruct journal entries from systems outside this repository: a bulk import of a historical work log, ticket references enriched into self-contained detail entries, and links repaired to point at systems that have since moved. Three independent modes, each callable on its own: Mode A (bulk import), Mode B (ticket enrichment), Mode C (external link migration). A common sequence runs Mode A first, then Mode B on selected tickets from the imported entries, then Mode C whenever an imported link points at a system that has since moved
- but nothing requires running them in that order or all three together.
Mindset
These entries reconstruct history that already happened somewhere else; the job is transcription and synthesis, not authorship. Reconstruct, do not invent - every claim traces to the source log, the ticket, or its comments. Each detail entry must stand alone: a reader understands the task without opening the ticket or the original log. Synthesise, don't transcribe - a reconstructed discussion reads as what was decided and why, never as a comment-by-comment transcript. Follow the Data and Privacy Policy on every entry regardless of mode. At batch scale, trust the filesystem over an agent's self-report, and recompute remaining work from the repository on every resume rather than from a saved list.
Know when this is the wrong tool: a brand-new entry documenting today's work is journal-entry-creator's job, not
this skill's. Repairing missing title/date frontmatter keys on entries that already exist in the repo's format
is the journal CLI's own one-pass pantheon-journal backfill command - a different problem from reconstructing
entries that do not exist yet, and this skill deliberately avoids that name to keep the two apart.
Prerequisites
This skill produces entries in the journal-entry-creator format and depends on it for the base frontmatter
schema, the tag taxonomy, and the structural validator
(journal-entry-creator/scripts/validate-journal-entry.sh). Read that skill's SKILL.md first if you have not
used it before - this skill assumes its conventions (triple-synced dates, single-H1 format, tag consistency) and
does not repeat them.
What ships with it
26 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.
- .tessl-plugin/plugin.json 641 B
- assets/schemas/ticket-detail-frontmatter.schema.json 3.4 KB
- assets/templates/ticket-detail-template.yaml 6.0 KB
- evals/instructions.json 3.2 KB
- evals/scenario-1/capability.txt 12 B
- evals/scenario-1/criteria.json 1.3 KB
- evals/scenario-1/task.md 2.3 KB
- evals/scenario-2/capability.txt 18 B
- evals/scenario-2/criteria.json 1.7 KB
- evals/scenario-2/task.md 2.8 KB
- evals/scenario-3/capability.txt 22 B
- evals/scenario-3/criteria.json 1.2 KB
- evals/scenario-3/task.md 2.4 KB
- evals/scenario-4/capability.txt 15 B
- evals/scenario-4/criteria.json 1.1 KB
- evals/scenario-4/task.md 2.3 KB
- evals/scenario-5/capability.txt 24 B
- evals/scenario-5/criteria.json 920 B
- evals/scenario-5/task.md 1.9 KB
- evals/summary.json 1.1 KB
- references/data-and-privacy-policy.md 2.3 KB
- references/mode-a-bulk-import.md 3.7 KB
- references/mode-b-ticket-enrichment.md 6.8 KB
- references/mode-c-link-migration.md 3.0 KB
- scripts/import-legacy-entries.sh 5.9 KB runs code
- scripts/validate-ticket-detail.sh 4.5 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.
- 6d ago First seen · 222 lines · 161 tokens per session scan A 13e9b3a83a2d
journal-entry-import is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed 2d ago), licensed MIT. It adds 161 tokens to every session and 2,997 once invoked, about $0.0008 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
obsidian-linear-sync
Mirror a Linear project one-way (Linear → Markdown, never back) into an Obsidian vault: one Markdown file per ticket under 01 Projects/Linear/ /, plus an index note with a linked ticket table, ticket references rewritten as wikilinks, comments below a divider, and a protected notes section that syncing never touches.…
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'…
A set of instructions for working with PDF files, which are documents designed to preserve their layout across devices.
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…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
slack-report-delivery
Deliver formatted network reports, audit results, topology diagrams, and compliance documentation to Slack channels with rich Block Kit formatting. Use when posting a health check report, sharing a security audit, delivering topology diagrams, or sending scheduled network reports to Slack.