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 agentlas-ai/agentlas-desktop --skill venue-templatesgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/venue-templates)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/venue-templates"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/venue-templates/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/agentlas-ai/agentlas-desktop/venue-templates"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/venue-templates.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.02593 |
| Opus 5.5 | $0.00023 | $0.01037 |
| Sonnet 5.5 | $0.00011 | $0.00519 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
venue-templates 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 1mo 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.
This is a copy
100% identical to venue-templates — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Venue Templates
Prepare publication and funding documents without treating stale formatting details as authoritative. This skill combines:
- a verification-first workflow for current venue rules;
- bundled LaTeX scaffolds for a small, explicit set of document types;
- writing-style and reviewer-expectation guides; and
- local helpers for discovering, copying, and inspecting templates.
Mandatory Currency Rule
Venue requirements are time-sensitive. Before giving exact page limits, deadlines, style-file names, anonymity rules, or required sections:
- Identify the exact venue, year or funding cycle, track, and article or proposal type.
- Open the official author instructions, call, solicitation, notice of funding opportunity (NOFO), or policy guide.
- Record the source URL and the date checked.
- Distinguish initial submission, revision/rebuttal, and camera-ready rules.
- Treat bundled files as scaffolds unless this skill explicitly says they are a copy of an official template.
Never infer a current style-file name by changing the year in an old filename. Never present a generic scaffold as an official venue template.
When to Use
Use this skill for:
- locating official journal or conference author instructions;
- checking page limits, required sections, anonymity, supplemental-material rules, or citation style;
- choosing and adapting a bundled LaTeX scaffold;
- preparing NSF, NIH, DOE, DARPA, or foundation proposal documents;
- designing a research poster after checking event-specific dimensions;
- adapting prose to a venue's audience and reviewer expectations; or
- inspecting a PDF's page count and embedded fonts.
Verification-First Workflow
1. Resolve the exact target
Ask for or derive:
- venue or funding agency;
- year/cycle and track;
- document type, such as research article, short paper, main track, R01, or R21;
- submission stage; and
- authoring format, such as LaTeX or Word.
Do not combine rules from similarly named venues or tracks.
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.
- assets/grants/nih_specific_aims.tex 9.0 KB
- assets/grants/nsf_proposal_template.tex 14 KB
- assets/journals/elsarticle-harv.bst 29 KB
- assets/journals/elsarticle-num-names.bst 28 KB
- assets/journals/elsarticle-num.bst 29 KB
- assets/journals/elsarticle-template-harv.tex 8.3 KB
- assets/journals/elsarticle-template-num-names.tex 8.2 KB
- assets/journals/elsarticle-template-num.tex 8.2 KB
- assets/journals/nature_article.tex 6.3 KB
- assets/journals/neurips_article.tex 9.1 KB
- assets/journals/plos_one.tex 12 KB
- assets/posters/beamerposter_academic.tex 8.4 KB
- references/cell_press_style.md 14 KB
- references/conferences_formatting.md 7.6 KB
- references/cs_conference_style.md 16 KB
- references/grants_requirements.md 9.9 KB
- references/journals_formatting.md 9.0 KB
- references/medical_journal_styles.md 16 KB
- references/ml_conference_style.md 18 KB
- references/nature_science_style.md 13 KB
- references/posters_guidelines.md 17 KB
- references/reviewer_expectations.md 16 KB
- references/venue_writing_styles.md 13 KB
- scripts/customize_template.py 6.7 KB runs code
- scripts/query_template.py 7.8 KB runs code
- scripts/validate_format.py 10 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.
- 1mo ago First seen · 287 lines · 57 tokens per session scan A 0635f0b7345d
venue-templates is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 2,593 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to venue-templates, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
cua-volume
Use Cua Volume, the one volume every Space and agent of this user shares. Inside a Space it is mounted as a folder (/volume on Linux, /Cua Volume on macOS), so any program reads and writes it directly. Use it for anything that must outlive this Space - your memory and outputs in your agent home, shared reference in…
doc-ingest
Extract readable text from document files — PDF, XLSX/CSV/TSV, DOCX, PPTX, and plain-text formats — so any task that arrives with an attachment can actually consume it.
md2pdf
Convert a Markdown file to PDF with GitHub-style formatting using the md2pdf tool.
delive-transcript-analyzer
Analyze, summarize, and extract insights from DeLive transcription sessions. Use when: user mentions DeLive, transcription, meeting transcripts, live captions, audio transcription, AI correction, corrected transcript, or transcript analysis; user wants to search, retrieve, summarize, correct, or process recorded…
hermesoffice-documents
Produce and edit Word documents in HermesOffice Docs — block editing, tracked changes, reports, and the templates/docs library (meeting notes, business plan, PRD, decision memo, and more). Load for any request that creates or restructures a document.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.