Borrowing it
Nothing to install: this file belongs to dallay/agentsync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dallay/agentsync/main/.agents/skills/makefile/SKILL.mdgit clone --depth 1 https://github.com/dallay/agentsyncWrote 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/dallay/agentsync/makefile)<a href="https://agentmods.dev/skills/dallay/agentsync/makefile"><img src="https://agentmods.dev/badge/skills/dallay/agentsync/makefile/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/dallay/agentsync/makefile"><img src="https://agentmods.dev/badge/skills/dallay/agentsync/makefile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01777 |
| Opus 5.5 | $0.00026 | $0.00711 |
| Sonnet 5.5 | $0.00013 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
makefile 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- makefile — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Creating a new
Makefilefor any project (C/C++, Go, Node.js, etc.) - Reviewing or refactoring existing makefiles for correctness and maintainability
- Debugging build failures related to make rules, prerequisites, or variables
- Setting up build automation with GNU Make (pattern rules, automatic dependencies, parallel builds)
- Ensuring portability across platforms or compliance with GNU Make conventions
Critical Patterns
- Tabs, Not Spaces: Every recipe line MUST start with a tab character. Spaces will cause a syntax error.
- Declare
.PHONY: Always mark non-file targets (e.g.,clean,all,test,install) with.PHONYto avoid conflicts with files of the same name. - Use
:=Over=When Possible: Prefer simple expansion (:=) for variables to avoid unexpected recursive expansion and improve performance. - Automatic Variables: Use
$@(target),$<(first prerequisite),$^(all prerequisites),$?(newer prerequisites), and$*(stem) in recipes to keep rules generic and reusable. - Use
$(wildcard ...)Not$(shell ls ...): Never shell out for file lists; use Make's built-in$(wildcard *.c)function instead. - Auto-Generate Dependencies: Use compiler flags like
-MMD -MPto generate.dfiles rather than maintaining header dependencies manually. - Clean Target: Always provide a
cleantarget and prefix destructive commands with-to ignore errors if files don't exist. - Variables First, Rules Second: Define all variables at the top, followed by the default goal, then build rules, then phony targets.
- Avoid Recursive Make: Don't use
$(MAKE) -C subdirunless absolutely necessary; prefer includes or non-recursive approaches.
File Structure
# -------------------------------------------------------
# Project: <name>
#
# Usage:
# make - Build the project
# make clean - Remove generated files
# make install - Install to $(PREFIX)
# make test - Run tests
#
# Variables:
# CC - C compiler (default: gcc)
# PREFIX - Installation prefix (default: /usr/local)
# -------------------------------------------------------
# --- Variables ---
CC ?= gcc
CFLAGS := -Wall -Wextra -O2
PREFIX ?= /usr/local
sources := $(wildcard src/*.c)
objects := $(sources:.c=.o)
deps := $(objects:.o=.d)
# --- Default Goal ---
all: program
# --- Build Rules ---
program: $(objects)
$(CC) -o $@ $^ $(LDFLAGS)
%.o: %.c
$(CC) $(CFLAGS) -MMD -MP -c $< -o $@
-include $(deps)
# --- Phony Targets ---
.PHONY: all clean install test
clean:
-rm -f program $(objects) $(deps)
install: program
install -d $(PREFIX)/bin
install -m 755 program $(PREFIX)/bin
test: program
./run-tests.sh
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.
- 1mo ago First seen · 260 lines · 64 tokens per session scan A d5db383b80da
makefile is a skill published in the GitHub repository dallay/agentsync (70 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,777 once invoked, about $0.0003 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.
Other skills, from other repositories
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
engineering-principles
Practical engineering judgement: smallest change, subtract before adding, data structures before logic, idempotent operations, migrate callers then delete. Use when designing, building, or reviewing changes.
financial-analysis
Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions. Use for statements, budgets, pricing, and diligence numbers.
scheduling
Scheduling across time zones: confirm times in the attendee's own zone, use IANA zone names, mind DST edges, buffers and calendar etiquette. Use when booking meetings or calls with people in other zones.
writing
Writing that sounds human: strip AI tells (em dashes, filler, hype, tacked-on tricolons), plain language, active voice, reader-first structure. Use when drafting or editing copy, docs, posts, or messages.