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 mohitmishra786/low-level-dev-skills --skill assembly-armgit clone --depth 1 https://github.com/mohitmishra786/low-level-dev-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/mohitmishra786/low-level-dev-skills/assembly-arm)<a href="https://agentmods.dev/skills/mohitmishra786/low-level-dev-skills/assembly-arm"><img src="https://agentmods.dev/badge/skills/mohitmishra786/low-level-dev-skills/assembly-arm/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/mohitmishra786/low-level-dev-skills/assembly-arm"><img src="https://agentmods.dev/badge/skills/mohitmishra786/low-level-dev-skills/assembly-arm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00101 | $0.02545 |
| Opus 5 | $0.00051 | $0.01273 |
| Sonnet 5 | $0.00020 | $0.00509 |
| Haiku 4.5 | $0.00010 | $0.00254 |
Grade A, and why
assembly-arm 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 8d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARM / AArch64 Assembly
Purpose
Guide agents through AArch64 (64-bit) and ARM (32-bit Thumb) assembly: registers, calling conventions, inline asm, and NEON/SVE SIMD patterns.
Triggers
- "How do I read ARM64 assembly output?"
- "What are the AArch64 registers and calling convention?"
- "How do I write inline asm for ARM?"
- "What is the difference between AArch64 and ARM Thumb?"
- "How do I use NEON intrinsics?"
Workflow
1. Generate ARM assembly
# AArch64 (native or cross-compile)
aarch64-linux-gnu-gcc -S -O2 foo.c -o foo.s
# 32-bit ARM Thumb
arm-linux-gnueabihf-gcc -S -O2 -mthumb foo.c -o foo.s
# From objdump
aarch64-linux-gnu-objdump -d -S prog
# From GDB on target
(gdb) disassemble /s main
2. AArch64 registers (AAPCS64)
| Register | Alias | Role |
|---|---|---|
x0–x7 |
— | Arguments 1–8 and return values |
x8 |
xr |
Indirect result location (struct return) |
x9–x15 |
— | Caller-saved temporaries |
x16–x17 |
ip0, ip1 |
Intra-procedure-call temporaries (used by linker) |
x18 |
pr |
Platform register (reserved on some OS) |
x19–x28 |
— | Callee-saved |
x29 |
fp |
Frame pointer (callee-saved) |
x30 |
lr |
Link register (return address) |
sp |
— | Stack pointer (must be 16-byte aligned at call) |
pc |
— | Program counter (not directly accessible) |
xzr |
wzr |
Zero register (reads as 0, writes discarded) |
v0–v7 |
q0–q7 |
FP/SIMD args and return |
v8–v15 |
— | Callee-saved SIMD (lower 64 bits only) |
v16–v31 |
— | Caller-saved temporaries |
Width variants: x0 (64-bit), w0 (32-bit, zero-extends to 64), h0 (16), b0 (8).
3. AAPCS64 calling convention
Integer/pointer args: x0–x7
Float/SIMD args: v0–v7
Return: x0 (int), x0+x1 (128-bit), v0 (float/SIMD)
Callee-saved: x19–x28, x29 (fp), x30 (lr), v8–v15 (lower 64 bits)
Caller-saved: everything else
Stack must be 16-byte aligned at any bl or blr instruction.
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.
- 8d ago First seen · 231 lines · 101 tokens per session scan A 8f952858dad3
assembly-arm is a skill published in the GitHub repository mohitmishra786/low-level-dev-skills (203 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 2,545 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
autohotkey-v2
Write AutoHotkey v2 desktop scripts for window management and Win32 integration; troubleshoot permissions and compile scripts with Ahk2Exe.
flow-launcher
Build Flow Launcher plugins with C# or Python JSON-RPC, configure plugin manifests, and integrate Everything search.
ast-refactoring-scripts
Use AST-aware tools such as libcst, ts-morph, or jscodeshift for repeatable code migrations across many files.
header-only-c-cpp-ingestion
Inspect C and C++ headers for public contracts and data structures before reading implementation files.
inline-lambda-functions
Use concise lambdas or arrow functions for small callbacks when a separate named function adds no clarity.
inline-type-signatures
Use native type annotations and avoid repeating the same type information in documentation comments.