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 TobiasBlask/open-paper-machine --skill coauthor-enginegit clone --depth 1 https://github.com/TobiasBlask/open-paper-machineWrote 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/tobiasblask/open-paper-machine/coauthor-engine)<a href="https://agentmods.dev/skills/tobiasblask/open-paper-machine/coauthor-engine"><img src="https://agentmods.dev/badge/skills/tobiasblask/open-paper-machine/coauthor-engine.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.00052 | $0.01605 |
| Opus 5 | $0.00026 | $0.00803 |
| Sonnet 5 | $0.00010 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
coauthor-engine 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Log: When this skill is activated, append a log entry to
outputs/orchestration_log.md:### Skill Activation: Co-Author Engine **Timestamp:** [current date/time] **Actor:** AI Agent (coauthor-engine) **Input:** [N] authors, task: [contribution tracking / responsibility assignment / CRediT statement] **Output:** author_contributions.md saved
Co-Author Engine
Core Principle
Modern academic publishing increasingly requires transparent documentation of who did what. The CRediT (Contributor Roles Taxonomy) system standardizes this. For AI-assisted papers, documenting the human-AI division of labor is not optional — it's becoming a requirement at major venues.
When to Activate
- User says "author contributions", "CRediT statement", "who did what"
- User says "add co-author", "assign responsibilities", "contribution tracking"
- Before submission (submission-engine may trigger this)
- When documenting AI involvement in the research process
Step 1: DEFINE Author Roster
Author Information Template
## Authors
| # | Name | Affiliation | Role | ORCID | Corresponding |
|---|------|-------------|------|-------|--------------|
| 1 | [Name] | [University/Org] | [Senior/Junior/PI] | [ORCID] | [Yes/No] |
| 2 | [Name] | [University/Org] | [Senior/Junior] | [ORCID] | [No] |
| 3 | AI Agent (Claude) | Anthropic | AI Assistant | N/A | No |
Author Order Conventions
- IS/Business conventions: First author did most work, last author is senior/PI
- CS conventions: First author did most work, alphabetical otherwise or by contribution
- Note: If AI is listed, typically in acknowledgments, not as author (venue-dependent)
Step 2: ASSIGN CRediT Roles
CRediT Taxonomy (14 Roles)
For each author (including AI), indicate contribution level:
| # | CRediT Role | Definition | Author 1 | Author 2 | AI Agent |
|---|---|---|---|---|---|
| 1 | Conceptualization | Ideas, formulation of research goals | Lead | Supporting | — |
| 2 | Data curation | Managing, annotating, maintaining data | Lead | — | Supporting |
| 3 | Formal analysis | Statistical, mathematical, computational analysis | Supporting | — | Lead |
| 4 | Funding acquisition | Obtaining financial support | — | Lead | — |
| 5 | Investigation | Conducting the research, data collection | Lead | Supporting | Supporting |
| 6 | Methodology | Development or design of methodology | Lead | Supporting | Supporting |
| 7 | Project administration | Managing and coordinating the project | Lead | — | — |
| 8 | Resources | Provision of study materials, tools, computing | — | Lead | — |
| 9 | Software | Programming, implementation, code | — | — | Lead |
| 10 | Supervision | Oversight and leadership responsibility | — | Lead | — |
| 11 | Validation | Verification and replication of results | Lead | Supporting | Supporting |
| 12 | Visualization | Creating figures, diagrams, plots | Supporting | — | Lead |
| 13 | Writing — original draft | Creating the initial manuscript | Supporting | — | Lead |
| 14 | Writing — review & editing | Critical review, commentary, revision | Lead | Lead | Supporting |
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 · 180 lines · 52 tokens per session scan A ca83c0a15896
coauthor-engine is a skill published in the GitHub repository TobiasBlask/open-paper-machine (18 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,605 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.