daily-coding

daily-coding is a skill for Claude Code from Galaxy-Dawn/claude-scholar. It costs 17 tokens per session (479 once invoked), scanned A, original, MIT.

A checklist for routine work that writes or changes source code.

In plain words
What is it for?
Use it when implementing features, adding code, or modifying existing source files.
Why use it?
It prompts the coding agent to read existing files first, make focused changes, consider common security risks, and verify the result.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-scholar plugin — 45 skills, 34 commands, 6 agents, 5 hooks shipped together

Good fit Use it when implementing features, adding code, or modifying existing source files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/galaxy-dawn/claude-scholar/daily-coding
About the project

Claude Scholar is a semi-automated research assistant for academic research and software development, supporting literature review, coding, experiments, reporting, writing, and project knowledge management. Computer science and AI researchers use it across the research workflow with several coding-agent platforms; the catalogue contains its skills, commands, agents, hooks, plugin, and instruction.

Galaxy-Dawn/claude-scholar · 5,917 stars · on GitHub

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 Galaxy-Dawn/claude-scholar --skill daily-coding
Clone the repo
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar

Made for: Claude Code.

Or install claude-scholar, the plugin that ships this one along with the rest of its 45 skills, 34 commands, 6 agents, 5 hooks.

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 daily-coding

README.md
[![agentmods](https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/daily-coding/github.svg)](https://agentmods.dev/skills/galaxy-dawn/claude-scholar/daily-coding)
Your own site
<a href="https://agentmods.dev/skills/galaxy-dawn/claude-scholar/daily-coding"><img src="https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/daily-coding/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 daily-coding

Your own site · 80×15
<a href="https://agentmods.dev/skills/galaxy-dawn/claude-scholar/daily-coding"><img src="https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/daily-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 479 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.00017 $0.00479
Opus 5.5 $0.00007 $0.00192
Sonnet 5.5 $0.00003 $0.00096
Haiku 4.5 $0.00002 $0.00048

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

Security

Grade A, and why

daily-coding 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.

skills/daily-coding/SKILL.md · 77 lines

What it actually says

Daily Coding Checklist

A minimal coding quality assurance checklist ensuring every code modification follows best practices.

When to Use

Use this skill for:

  • Implementing new features
  • Adding code or modifying existing code
  • User requests like "write a...", "implement...", "add...", or "modify..."
  • Any coding task that involves Edit or Write tools

When Not to Use

Do not use this skill for:

  • Pure reading or understanding tasks with no modification intent
  • Work already covered by specialized skills such as bug-detective, architecture-design, or verification-loop
  • Configuration-only changes
  • Documentation-only writing

Core Checklist

Before Starting

  • Read before modify - Must read target file with Read tool before making changes
  • Understand context - Confirm understanding of existing code logic and design intent

During Coding

  • Minimal changes - Only change what's necessary, no over-engineering, no unrelated features
  • Type safety - Add type hints for Python, avoid any in TypeScript
  • Security check - Avoid command injection, XSS, SQL injection vulnerabilities

After Completion

  • Verify execution - Ensure code runs correctly with no syntax errors
  • Clean up - Remove print/console.log debug statements and temporary files
  • Brief summary - Inform user what was changed and the scope of impact

Quick Reference

Common Mistakes to Avoid

# ❌ Don't
def process(data=[]):  # Mutable default argument
    pass

# ✅ Should
def process(data: list | None = None):
    data = data or []
# ❌ Don't
except:  # Bare except
    pass

# ✅ Should
except ValueError as e:
    logger.error(f"Processing failed: {e}")
    raise

Security Check Points

  • User input must be validated/escaped
  • Use pathlib for file paths, avoid path traversal
  • Never hardcode sensitive info (API keys, passwords)
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 · 77 lines · 17 tokens per session scan A dc9f72ac0b04

Subscribe to this mod's changes

daily-coding is a skill published in the GitHub repository Galaxy-Dawn/claude-scholar (5,917 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 479 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-08-30.

Related

Other skills, from other repositories

daily-coding

Daily coding assistant that auto-triggers when writing/modifying code, providing a core checklist. ✅ Trigger scenarios: Implementing new features, adding code, modifying existing code User requests "write a...", "implement...", "add...", "modify..." Any coding task involving Edit/Write tools ❌ Does not trigger: Pure…

HaipingXu/social-science-claude-scholar · 110 tokens

kami-deck

A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.

nexu-io/open-design · 49 tokens

improve-rule

Use when reviewing or improving a Front-End Checklist rule MDX file to raise its quality score, fix stub prompts, add missing fields, or enrich content with real code examples.

thedaviddias/Front-End-Checklist · 39 tokens

html-size

Use when auditing page weight for crawl efficiency, investigating why certain page content is not appearing in Google's index, or reviewing server-rendered pages that embed large JSON payloads in HTML.

thedaviddias/Front-End-Checklist · 39 tokens

image-file-size

Use when auditing the image pipeline, static assets in public/, CMS-managed media, or image CDN transforms. Separate file-size problems from dimension mismatches so you can tell whether the issue is compression, format choice, or responsive delivery.

thedaviddias/Front-End-Checklist · 52 tokens

aria-roles

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use valid ARIA role values. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

thedaviddias/Front-End-Checklist · 49 tokens