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 skills/aristoteleo/pantheonos/workflownpx skills add aristoteleo/PantheonOS --skill workflowgit clone --depth 1 https://github.com/aristoteleo/PantheonOSWrote 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/aristoteleo/pantheonos/workflow)<a href="https://agentmods.dev/skills/aristoteleo/pantheonos/workflow"><img src="https://agentmods.dev/badge/skills/aristoteleo/pantheonos/workflow.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.00058 | $0.01924 |
| Opus 5 | $0.00029 | $0.00962 |
| Sonnet 5 | $0.00012 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
Paper Writing Workflow 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paper Writing Workflow
Workflow phases decide the order of work. They do not provide final prose style or visual themes. Use only the phases relevant to the current scenario; not every task needs every phase.
| Phase | When to run | Output file |
|---|---|---|
| 1. Triage | every task; whenever user intent changes | {workdir}/triage.md |
| 2. Material inventory | user supplied files, notes, data, figures, comments | {workdir}/materials/inventory.md |
| 3. Research question | early papers, grants, vague topics; before outline | {workdir}/research_question.md |
| 4. Literature review | claims need citation grounding or novelty positioning | {workdir}/literature_matrix.md |
| 5. Paper outline | before drafting any full manuscript, grant, or report | {workdir}/outline.md |
| 6. Data analysis summary | user provides result tables, plots, statistics, experiment notes | {workdir}/results_table.md |
| 7. Figure storyline | figures/tables carry the core story | {workdir}/figures_plan.md |
| 8. Reader testing | before finalizing high-stakes documents or after major rewrites | {workdir}/reader_test.md |
| 9. Finalize packet | before ending a full task | {workdir}/final_state.md |
Phases tied to a single scenario live in that scenario file:
- Revision / rebuttal loop → ../scenarios/revision_response.md
- Knowledge lineage / novelty audit → ../scenarios/grant_proposal.md
1. Triage
Use at the start of every paper-writing task and whenever user intent changes.
Output
Create or update triage.md:
scenario_id: paper_submission
format_id: journal_article
theme_id: editable_article
mode: report # report (default) | submission — see Mode section in SKILL.md
language: zh
audience: reviewers
source_materials:
- materials/inventory.md
output:
markdown_source: draft/paper.md
html_path: report/paper_preview.html
editable_html: true
pdf: true
docx: false
latex: false
constraints:
venue_profile: null
page_size: A4
word_limits: null
quality_gates:
- manuscript_coverage
- format_lint
- reproducibility
- html_editability_check
# submission mode only:
# - claim_evidence_check
# - reviewer_rubric
# - reporting_guideline_check (clinical only)
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 · 254 lines · 58 tokens per session scan A 7b51c3c50734
Paper Writing Workflow is a skill published in the GitHub repository aristoteleo/PantheonOS (482 stars, last pushed 3d ago), licensed BSD-2-Clause. It adds 58 tokens to every session and 1,924 once invoked, about $0.0003 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 skills, from other repositories
search
Search local or remote sources quickly, narrow results, and surface the highest-signal matches for the task.
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
create_profile_style_skill
【META SKILL】分析当前剪辑逻辑与风格，总结并生成一个新的可复用 Skill 文件，存入剪辑技能库。Analyze the current editing logic and style, summarize and generate a new reusable Skill file, and store it in the editing skill library.
Security Audit Reporter
Triage raw security-scan findings (hardcoded secrets, injection patterns, vulnerable dependencies) into a prioritized, actionable security audit report. Use for security audit, code audit, vulnerability triage, and risk review.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.