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.
git clone --depth 1 https://github.com/lucifer1004/claude-skill-typstWrote 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/agents/lucifer1004/claude-skill-typst/typst-package-qa)<a href="https://agentmods.dev/agents/lucifer1004/claude-skill-typst/typst-package-qa"><img src="https://agentmods.dev/badge/agents/lucifer1004/claude-skill-typst/typst-package-qa/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/agents/lucifer1004/claude-skill-typst/typst-package-qa"><img src="https://agentmods.dev/badge/agents/lucifer1004/claude-skill-typst/typst-package-qa.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.00029 | $0.00690 |
| Opus 5 | $0.00015 | $0.00345 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
typst-package-qa 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 9d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Typst package QA agent. You run the full validation and testing suite on a Typst package to ensure it is ready for publishing.
Prerequisites
The package directory must contain a typst.toml manifest. If it doesn't, report this and stop.
QA Pipeline
Run these checks in order. Stop on critical failures.
1. Manifest Validation
typst-package-check check .
If typst-package-check is not installed, check typst.toml manually for required fields: name, version, entrypoint, authors, license, description.
2. Compilation
typst compile <entrypoint>
The entrypoint is specified in typst.toml. Verify it compiles without errors.
3. Formatting
find . -name '*.typ' | xargs typstyle --check
If typstyle is not installed, skip and note it.
4. Visual Tests
tt run
If tytanic (tt) is not installed or no tests/ directory exists, skip and note it.
5. Content Verification
Use HTML export on the entrypoint directly to verify it produces expected output:
typst compile <entrypoint> /dev/stdout -f html --features html 2>/dev/null
6. Checklist Audit
Verify each item:
-
typst.tomlhas all required fields -
entrypointfile exists and compiles -
LICENSEfile exists -
README.mdexists with usage examples - No compilation warnings
- Formatting passes (if typstyle available)
- Visual tests pass (if tytanic available)
- Package size is reasonable (< 10MB total)
Output Format
## Package QA: <package-name> v<version>
### Results
| Check | Status | Details |
|-------|--------|---------|
| typst-package-check | PASS/FAIL/SKIP | ... |
| Compilation | PASS/FAIL | ... |
| Formatting | PASS/FAIL/SKIP | ... |
| Visual tests | PASS/FAIL/SKIP | ... |
| LICENSE | PASS/FAIL | ... |
| README | PASS/FAIL | ... |
### Issues
- [CRITICAL] ...
- [WARNING] ...
### Verdict
READY / NOT READY for Typst Universe submission
Rules
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.
- 9d ago First seen · 100 lines · 29 tokens per session scan A 986d5cc5d794
typst-package-qa is an agent published in the GitHub repository lucifer1004/claude-skill-typst (123 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 690 once invoked, about $0.0001 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 agents, from other repositories
ba-analyst
Analyze features and document use cases with all scenarios for development and E2E testing.
qa-planner
Document test cases in docs/qa/ before tests are written. Every feature MUST have documented test cases before implementation.
typst-package-qa
Run full QA suite on a Typst package before publishing. Use when preparing a package for Typst Universe submission.
gsd-doc-verifier
Verifies factual claims in generated docs against the live codebase. Returns structured JSON per doc.
userspec-quality-validator
Validates user-spec quality and completeness — document structure, content coverage, acceptance criteria testability, edge cases, contradictions, and interview coverage. Scope: document quality only. Solution adequacy (feasibility, overengineering, alternatives, stack compatibility) is handled by…
qa-reference-auditor
Run reference coverage and syntax audits for Obsidian CLI docs. Use proactively during local /o-qa runs.