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 Jody09-dotcom/constructionx-skills --skill site-diarygit clone --depth 1 https://github.com/Jody09-dotcom/constructionx-skillsWrote 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/jody09-dotcom/constructionx-skills/site-diary)<a href="https://agentmods.dev/skills/jody09-dotcom/constructionx-skills/site-diary"><img src="https://agentmods.dev/badge/skills/jody09-dotcom/constructionx-skills/site-diary/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/jody09-dotcom/constructionx-skills/site-diary"><img src="https://agentmods.dev/badge/skills/jody09-dotcom/constructionx-skills/site-diary.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.00076 | $0.01103 |
| Opus 5 | $0.00038 | $0.00551 |
| Sonnet 5 | $0.00015 | $0.00221 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
site-diary 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Diary
This skill produces a UK construction site diary for a single day from a short verbal or typed brief. It follows conventions used by CITB-trained site managers and main contractors. The diary is a draft. The site manager or project manager reviews, signs, and files it.
When to Use
- End of day on site, writing up the day's works
- Morning after, filling in yesterday's diary from notes
- Back-filling missed days before a monthly report or claim
- Preparing records for a delay claim, variation, or dispute
Workflow
Phase 1, gather inputs.
Ask the user for the following. If anything is missing, ask one short follow-up question, do not guess.
- Date (default to today if user says "today")
- Site name or project name
- Site reference or job number, if used
- Site manager name (for sign-off)
- Weather through the day (am and pm, temperature, rain, wind)
- Labour breakdown, direct employed vs subcontractors, by trade
- Plant and equipment on site (excavator, scaffold, scissor lift, etc.)
- Deliveries received (time, supplier, material)
- Works completed by trade
- Delays, with reason (weather, delivery, design info, subbie no-show, etc.)
- Incidents or near-misses (RIDDOR reportable flagged)
- Visitors (name, company, reason, time in/out)
- Photos taken (count and subjects, consent status for any workers in frame)
Phase 2, produce the diary.
Fill the template below. Use plain English. Keep trade labels standard (bricklayer, groundworker, carpenter, electrician, plumber, plasterer, labourer, scaffolder, etc.). If a field has no entry, write "None" rather than leaving it blank.
Phase 3, save.
Save the diary as markdown to the user-specified path. Default path: site-diaries/{site-slug}/{YYYY-MM-DD}-site-diary.md. Create the folder if missing. Confirm the save path back to the user.
Diary Template
# Site Diary, {Site Name}
**Date:** {YYYY-MM-DD}
**Job Reference:** {ref or "n/a"}
**Site Manager:** {Name}
**Weather AM:** {conditions, temp}
**Weather PM:** {conditions, temp}
## Labour on Site
| Trade | Direct | Subcontractor | Total |
|-------|--------|---------------|-------|
| ... | ... | ... | ... |
**Total on site:** {number}
## Plant and Equipment
- {item, owner, in/out}
## Deliveries
| Time | Supplier | Material | Qty | Notes |
|------|----------|----------|-----|-------|
| ... | ... | ... | ... | ... |
## Works Completed
- {trade}: {description of works}
- ...
## Delays
| Delay | Reason | Hours Lost | Follow-up |
|-------|--------|------------|-----------|
| ... | ... | ... | ... |
## Incidents and Near-Misses
- {time, description, persons involved, action taken, RIDDOR reportable y/n}
If none: "No incidents or near-misses reported."
## Visitors
| Time In | Time Out | Name | Company | Reason | Inducted |
|---------|----------|------|---------|--------|----------|
| ... | ... | ... | ... | ... | ... |
## Photos
- {count} photos taken. Subjects: {list}. Consent obtained for all workers in frame: {y/n}.
## Notes
{Free-text notes, observations, items for tomorrow.}
---
Drafted by site diary skill. Reviewed and signed by:
**{Site Manager Name}** ______________________ **Date:** ______________
What ships with it
1 file 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.
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 · 131 lines · 76 tokens per session scan A b5a906dbfda5
site-diary is a skill published in the GitHub repository Jody09-dotcom/constructionx-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,103 once invoked, about $0.0004 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-31.
Other skills, from other repositories
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
Statutory Interpretation
Use when applying a disciplined analytical method to parse and interpret a statutory, regulatory, or contractual provision — mapping structure, defined terms, and competing readings — to produce a structured interpretation worksheet for attorney review.
hardening
A set of Linux instructions for hardening systems, meaning reducing unsafe settings and limiting unnecessary access.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
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…
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.