submittal-tracker

submittal-tracker is a skill for Claude Code, Codex from datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction. It costs 24 tokens per session (1,236 once invoked), scanned A, original, MIT.

A tracker for construction submittals, which are project documents sent for review before work or materials are approved.

In plain words
What is it for?
It helps manage product data, shop drawings, samples, mock-ups, certificates, and test reports from draft through approval or rejection.
Why use it?
It keeps approvals, revisions, review comments, and required dates in one workflow so items are less likely to delay the project.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit It helps manage product data, shop drawings, samples, mock-ups, certificates, and test reports from draft through approval or rejection.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker
Install

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.

Any agent
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill submittal-tracker
Clone the repo
git clone --depth 1 https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction

Made for: Claude Code, Codex.

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 submittal-tracker

README.md
[![agentmods](https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker/github.svg)](https://agentmods.dev/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker)
Your own site
<a href="https://agentmods.dev/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker/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 submittal-tracker

Your own site · 80×15
<a href="https://agentmods.dev/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/submittal-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,236 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00024 $0.01236
Opus 5.5 $0.00010 $0.00494
Sonnet 5.5 $0.00005 $0.00247
Haiku 4.5 $0.00002 $0.00124

Measured 1mo ago against content hash cb03acbf312d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

submittal-tracker 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

1_DDC_Toolkit/Document-Control/submittal-tracker/SKILL.md · 154 lines

How it starts

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

Submittal Tracker

Business Case

Submittals require careful tracking to avoid delays. This skill manages the entire submittal workflow from creation to approval.

Technical Implementation

import pandas as pd
from datetime import datetime, date, timedelta
from typing import Dict, Any, List, Optional
from dataclasses import dataclass, field
from enum import Enum


class SubmittalStatus(Enum):
    DRAFT = "draft"
    SUBMITTED = "submitted"
    UNDER_REVIEW = "under_review"
    APPROVED = "approved"
    APPROVED_AS_NOTED = "approved_as_noted"
    REVISE_RESUBMIT = "revise_resubmit"
    REJECTED = "rejected"


class SubmittalType(Enum):
    PRODUCT_DATA = "product_data"
    SHOP_DRAWING = "shop_drawing"
    SAMPLE = "sample"
    MOCK_UP = "mock_up"
    CERTIFICATE = "certificate"
    TEST_REPORT = "test_report"


@dataclass
class ReviewComment:
    reviewer: str
    comment: str
    comment_date: date
    resolved: bool = False


@dataclass
class Submittal:
    submittal_id: str
    spec_section: str
    title: str
    submittal_type: SubmittalType
    status: SubmittalStatus
    contractor: str
    revision: int
    submitted_date: Optional[date]
    required_date: date
    approved_date: Optional[date] = None
    comments: List[ReviewComment] = field(default_factory=list)
    files: List[str] = field(default_factory=list)


class SubmittalTracker:
    def __init__(self, project_name: str):
        self.project_name = project_name
        self.submittals: Dict[str, Submittal] = {}
        self._counter = 0

    def create_submittal(self, spec_section: str, title: str,
                        submittal_type: SubmittalType, contractor: str,
                        required_date: date) -> Submittal:
        self._counter += 1
        sub_id = f"SUB-{self._counter:04d}"

        submittal = Submittal(
            submittal_id=sub_id,
            spec_section=spec_section,
            title=title,
            submittal_type=submittal_type,
            status=SubmittalStatus.DRAFT,
            contractor=contractor,
            revision=0,
            submitted_date=None,
            required_date=required_date
        )
        self.submittals[sub_id] = submittal
        return submittal

    def submit(self, sub_id: str, files: List[str]):
        if sub_id in self.submittals:
            self.submittals[sub_id].status = SubmittalStatus.SUBMITTED
            self.submittals[sub_id].submitted_date = date.today()
            self.submittals[sub_id].files = files

    def review(self, sub_id: str, status: SubmittalStatus, reviewer: str, comment: str = ""):
        if sub_id in self.submittals:
            sub = self.submittals[sub_id]
            sub.status = status
            if comment:
                sub.comments.append(ReviewComment(reviewer, comment, date.today()))
            if status in [SubmittalStatus.APPROVED, SubmittalStatus.APPROVED_AS_NOTED]:
                sub.approved_date = date.today()

    def resubmit(self, sub_id: str, files: List[str]):
        if sub_id in self.submittals:
            sub = self.submittals[sub_id]
            sub.revision += 1
            sub.status = SubmittalStatus.SUBMITTED
            sub.submitted_date = date.today()
            sub.files = files

    def get_pending(self) -> List[Submittal]:
        return [s for s in self.submittals.values()
                if s.status in [SubmittalStatus.SUBMITTED, SubmittalStatus.UNDER_REVIEW]]

    def get_overdue(self) -> List[Submittal]:
        today = date.today()
        return [s for s in self.submittals.values()
                if s.status not in [SubmittalStatus.APPROVED, SubmittalStatus.APPROVED_AS_NOTED]
                and s.required_date < today]

    def export_log(self, output_path: str):
        data = [{
            'ID': s.submittal_id,
            'Spec': s.spec_section,
            'Title': s.title,
            'Type': s.submittal_type.value,
            'Status': s.status.value,
            'Rev': s.revision,
            'Submitted': s.submitted_date,
            'Required': s.required_date,
            'Approved': s.approved_date
        } for s in self.submittals.values()]
        pd.DataFrame(data).to_excel(output_path, index=False)

Read the full file on GitHub · 154 lines

Files

What ships with it

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

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. 1mo ago First seen · 154 lines · 24 tokens per session scan A cb03acbf312d

Subscribe to this mod's changes

submittal-tracker is a skill published in the GitHub repository datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction (373 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 1,236 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

process-mapper

Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…

alirezarezvani/claude-skills · 176 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens

scenario-team-admin

Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and…

scenario-labs/skills · 101 tokens

rice-impact-matrix

Califica iniciativas usando tanto RICE como alineación estratégica para una priorización matizada. Úsalo cuando te pidan priorizar características, construir una matriz de prioridades, combinar puntuación cuantitativa con ajuste estratégico, o decidir qué construir después con múltiples iniciativas en competencia.…

mohitagw15856/pm-claude-skills · 93 tokens

requirement-forge-refiner

Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…

techygarg/lattice · 121 tokens