TezAtlas: Command for Claude Code

.claude/commands/submission-check.md

submission-check is a command for Claude Code from tialkan/TezAtlas. It costs 0 tokens per session (1,530 once invoked), scanned A, original, MIT.

A pre-submission checklist command for academic or institutional work. It reads project status, checks the target journal, conference, or institution, and reviews the document before submission.

In plain words
What is it for?
Use it to check submission context, document type, word count, template, output format, and applicable venue requirements.
Why use it?
It helps catch missing venue requirements and unfinished writing before work is sent to a journal, conference, or institution.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is tialkan/TezAtlas's own configuration. It tells Claude Code how to work on TezAtlas itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything TezAtlas configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tialkan/TezAtlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tialkan/TezAtlas/main/.claude/commands/submission-check.md
Clone the repo
git clone --depth 1 https://github.com/tialkan/TezAtlas

Made for: Claude Code.

Wrote 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.

agentmods badge for submission-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/tialkan/tezatlas/submission-check/github.svg)](https://agentmods.dev/commands/tialkan/tezatlas/submission-check)
Your own site
<a href="https://agentmods.dev/commands/tialkan/tezatlas/submission-check"><img src="https://agentmods.dev/badge/commands/tialkan/tezatlas/submission-check/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.

agentmods 80×15 button for submission-check

Your own site · 80×15
<a href="https://agentmods.dev/commands/tialkan/tezatlas/submission-check"><img src="https://agentmods.dev/badge/commands/tialkan/tezatlas/submission-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01530
Opus 5.5 $0.00000 $0.00612
Sonnet 5.5 $0.00000 $0.00306
Haiku 4.5 $0.00000 $0.00153

Measured today against content hash 461891ebf01d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

submission-check 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 today.

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.

.claude/commands/submission-check.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are TezAtlas in Submission Check mode. The user has typed /submission-check.

This command runs a pre-submission checklist before the user sends their work to a journal, conference, or institution.


Step 1 — Load Context

Read STATUS.md to determine:

  • document_type
  • target_venue (journal name, conference, institution) — if set
  • writing_stats.total_words
  • latex_template / output_format
  • Current phase

If phase < 6 (writing not complete):

⚠️  Yazım fazı henüz tamamlanmamış (Faz [N]).
Teslim kontrolü genellikle son revizyondan sonra yapılır.
Yine de devam etmek ister misiniz? (E/H)

Step 2 — Venue Requirements

Ask if not already in STATUS.md:

Teslim hedefi nedir?
A) Dergi — dergi adını yazın
B) Konferans — konferans adını yazın
C) Üniversite — tez teslimi (YÖK / kurum kuralları)
D) Diğer — açıklayın

If a specific journal/conference is named, use known requirements if available. Otherwise use the document type defaults below.


Step 3 — Run Checklist

Display results as a structured checklist:

╔═══════════════════════════════════════════════════╗
║  Teslim Kontrolü — [DOCUMENT_TYPE] → [VENUE]      ║
╠═══════════════════════════════════════════════════╣
║  ZORUNLU (MANDATORY)                              ║
╠═══════════════════════════════════════════════════╣

A) Word / Page Count

Belge Türü Tipik Limit Kontrol
Dergi makalesi 6,000–10,000 kelime writing_stats.total_words
Konferans bildirisi 4,000–6,000 kelime idem
Doktora tezi 60,000–100,000 kelime idem
Yüksek lisans tezi 30,000–60,000 kelime idem

Check and report: ✅ / ⚠️ (close to limit) / ❌ (over limit)

B) Abstract

  • Abstract mevcut mu? (Kaynak: draft/abstract.md veya ilgili bölüm)
  • Kelime limiti uygun mu? (Genellikle 150–300 kelime)
  • Anahtar kelimeler eklenmiş mi? (3–6 adet)

C) Citation Completeness

Run: Check references.bib exists and is non-empty.

  • references.bib mevcut
  • Tüm \cite{} veya [@key] çağrıları .bib'de karşılık buluyor
  • BibTeX formatı geçerli (virgül, parantez hataları yok)

Read the full file on GitHub · 186 lines

Changes

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.

  1. today First seen · 186 lines · 0 tokens per session scan A 461891ebf01d

Subscribe to this mod's changes

submission-check is a command published in the GitHub repository tialkan/TezAtlas (33 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,530 tokens. 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-11-07.

Related

submission-check compared with commands from other repositories

submission-check next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
submission-checktialkan/TezAtlasCommand3312d agoMITA0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
speckit.bug.testgithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code