Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
Linker and Link-Time Optimisation (LTO) skill. An agent skill from mohitmishra786/low-level-dev-skills.
MITAuto-check passed
Install Linkers Lto
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-lto --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/binaries/linkers-lto .claude/skills/linkers-lto && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .claude/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-ltoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-lto --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/binaries/linkers-lto .agents/skills/linkers-lto && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .agents/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-lto --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/binaries/linkers-lto .cursor/skills/linkers-lto && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .cursor/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitmishra786/low-level-dev-skills.git --path skills/binaries/linkers-lto--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-lto --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/binaries/linkers-lto .gemini/skills/linkers-lto && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .gemini/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-ltoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/binaries/linkers-lto .github/skills/linkers-lto && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .github/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitmishra786/low-level-dev-skills linkers-lto --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/binaries/linkers-lto .opencode/skills/linkers-lto && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkers-lto" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/binaries/linkers-lto into .opencode/skills/linkers-lto/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkers-lto", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linkers-lto- GitHub stars
- 252
- Token cost
- ~1.4k tokens
- SKILL.md length
- 316 words
- Files
- 2 (incl. references)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- MIT
At a glance
Linker and Link-Time Optimisation (LTO) skill. An agent skill from mohitmishra786/low-level-dev-skills.
- Works in 9 steps: Linker selection → Essential linker flags → Link order matters (GNU ld) → …
- Configuring GNU ld
- SKILL.md covers Purpose, Triggers, Workflow and Related skills
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Linkers Lto is an agent skill from mohitmishra786/low-level-dev-skills. Linker and Link-Time Optimisation (LTO) skill. Use when configuring GNU ld, gold, or lld linker flags, diagnosing link-order issues or undefined symbols at link time, enabling LTO safely in real projects, or understanding inter-module optimisation trade-offs. Activates on queries about linker flags, -flto, thin LTO, LTCG, --gc-sections, link order errors, weak symbols, or linker scripts.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/flags.md`).
The repository describes itself as: A curated suite of AI agent skills for systems and low-level programming with C/C++, Rust, and Zig toolchains, covering compilers, debuggers, profilers, build systems…. The licence is MIT.
When your agent uses it
- Configuring GNU ld
- Lld linker flags
- Diagnosing link-order issues
- Undefined symbols at link time
Example prompts
- “/linkers-lto”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bdc5847. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linkers Lto loads about 1.4k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 316 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitmishra786/low-level-dev-skills at commit bdc5847, republished under its MIT licence (© mohitmishra786). 316 words, ~1,412 tokens.
Download SKILL.mdSave it as
.claude/skills/linkers-lto/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- linkers-lto
- description
- Linker and Link-Time Optimisation (LTO) skill. Use when configuring GNU ld, gold, or lld linker flags, diagnosing link-order issues or undefined symbols at link time, enabling LTO safely in real projects, or understanding inter-module optimisation trade-offs. Activates on queries about linker flags, -flto, thin LTO, LTCG, --gc-sections, link order errors, weak symbols, or linker scripts.
Linkers and LTO
Purpose
Guide agents through linker selection, common linker flags, link-order issues, LTO setup, and symbol-visibility management.
Triggers
- "I'm getting
undefined referenceat link time" - "How do I enable LTO for a real project?"
- "Which linker should I use: ld, gold, or lld?"
- "How do I reduce binary size with
--gc-sections?" - "How do I write or understand a linker script?"
- "I have duplicate symbol or weak symbol issues"
Workflow
1. Linker selection
| Linker | Invocation | Strengths |
|---|---|---|
| GNU ld (BFD) | default on Linux | Universal, stable |
| gold | -fuse-ld=gold | Faster than ld for C++; supports LTO plugins |
| lld (LLVM) | -fuse-ld=lld | Fastest, parallel, required for Clang LTO |
# Use lld with GCC or Clang
gcc -fuse-ld=lld -o prog ...
clang -fuse-ld=lld -o prog ...
# Check which linker is used
gcc -v -o prog main.c 2>&1 | grep 'Invoking'2. Essential linker flags
# Pass linker flags via compiler driver:
# -Wl,flag1,flag2 (comma-separated, no spaces)
# -Wl,flag1 -Wl,flag2 (separate -Wl options)
gcc main.c -o prog \
-Wl,-rpath,/opt/mylibs/lib \ # runtime library search path
-Wl,--as-needed \ # only link libraries that are actually used
-Wl,--gc-sections \ # remove unused sections (requires -ffunction-sections -fdata-sections)
-Wl,-z,relro \ # mark relocations read-only after startup
-Wl,-z,now \ # resolve all symbols at startup (full RELRO)
-L/opt/mylibs/lib -lfoo3. Link order matters (GNU ld)
GNU ld processes archives left-to-right. A library must come after the objects that need it.
# Wrong: libfoo provides symbols needed by main.o
gcc main.o -lfoo libdep.a -o prog # can fail if libdep.a needs libfoo
# Correct: dependencies after dependents
gcc main.o -lfoo -ldep -o prog
# If there are circular deps between archives:
gcc main.o -Wl,--start-group -lfoo -lbar -Wl,--end-group -o prog
# --start-group/--end-group: repeat search until no new symbols resolved4. LTO with GCC
# Compile
gcc -O2 -flto -ffunction-sections -fdata-sections -c foo.c -o foo.o
gcc -O2 -flto -ffunction-sections -fdata-sections -c bar.c -o bar.o
# Link (must pass -flto again)
gcc -O2 -flto -Wl,--gc-sections foo.o bar.o -o prog
# Archives: must use gcc-ar / gcc-ranlib, not plain ar
gcc-ar rcs libfoo.a foo.o
gcc-ranlib libfoo.aParallel LTO:
gcc -O2 -flto=auto foo.o bar.o -o prog # uses jobserver
gcc -O2 -flto=4 foo.o bar.o -o prog # 4 parallel jobs5. LTO with Clang / lld
# Full LTO
clang -O2 -flto -fuse-ld=lld foo.c bar.c -o prog
# ThinLTO (faster, nearly same quality)
clang -O2 -flto=thin -fuse-ld=lld foo.c bar.c -o prog
# LTO with cmake: set globally
set(CMAKE_INTERPROCEDURAL_OPTIMIZATION ON) # enables -fltoThinLTO caches work: subsequent builds that reuse unchanged modules are faster.
Cache location: specify with -Wl,--thinlto-cache-dir=/tmp/thinlto-cache.
6. Dead-code stripping
# Compile with per-function/per-data sections
gcc -O2 -ffunction-sections -fdata-sections -c foo.c -o foo.o
# Link with garbage collection
gcc -Wl,--gc-sections foo.o -o prog
# Verify what was removed
gcc -Wl,--gc-sections -Wl,--print-gc-sections foo.o -o prog 2>&1 | head -20On macOS, the linker strips dead code by default (-dead_strip).
7. Symbol visibility
Controlling visibility reduces DSO size and enables better LTO:
# Hide all symbols by default, export explicitly
gcc -fvisibility=hidden -O2 -shared -fPIC foo.c -o libfoo.so
# In source, mark exports:
__attribute__((visibility("default"))) int my_public_function(void);Or use a version script:
# foo.ver
{
global: my_public_function; my_other_public;
local: *;
};gcc -Wl,--version-script=foo.ver -shared -fPIC -o libfoo.so foo.o8. Common linker errors
| Error | Cause | Fix |
|---|---|---|
undefined reference to 'foo' | Missing library or wrong order | Add -lfoo; move after the object that needs it |
multiple definition of 'foo' | Symbol defined in two TUs | Remove duplicate; use static or extern |
cannot find -lfoo | Library not in search path | Add -L/path/to/lib; install dev package |
relocation truncated | Address overflow in relocation | Use -mcmodel=large; restructure image |
version 'GLIBC_2.33' not found | Binary needs newer glibc | Link statically or rebuild on older host |
circular reference | Archives mutually depend | Use --start-group/--end-group |
9. Linker map file
# Generate a map file (shows symbol → section → file)
gcc -Wl,-Map=prog.map -o prog foo.o bar.o
less prog.mapUseful for debugging binary size and symbol placement.
For a comprehensive linker and LTO flags reference, see references/flags.md.
Related skills
- Use
skills/binaries/elf-inspectionfor examining the resulting binary - Use
skills/compilers/gccorskills/compilers/clangfor compile-phase LTO flags - Use
skills/binaries/binutilsforar,strip,objcopy
© mohitmishra786, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/binaries/linkers-lto of mohitmishra786/low-level-dev-skills.
- SKILL.md
- references/flags.md
Open the folder on GitHubat commit bdc5847
Compare with similar skills
Linkers Lto next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linkers Lto this skillmohitmishra786/low-level-dev-skills | 252 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Configure Channelopenclaw/openclaw | 392k | — | ~946 | Automated safety check: Pass | MIT | |
| Internal Linksthedaviddias/Front-End-Checklist | 74k | — | ~770 | Automated safety check: Pass | MIT | |
| External Linksthedaviddias/Front-End-Checklist | 74k | — | ~773 | Automated safety check: Pass | MIT | |
| Invalid Linksthedaviddias/Front-End-Checklist | 74k | — | ~806 | Automated safety check: Pass | MIT | |
| ConfigurationBuilderIO/agent-native | 7.1k | — | ~2.1k | Automated safety check: Pass | None |
Similar skills
Internal Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or…
External Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes…
Invalid Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links…
Configuration
BuilderIO/agent-native
Where a configuration value belongs — app config schema, agent-native.config.ts, or an environment variable — and how the layers resolve.
SEO Aeo Internal Linking
sickn33/agentic-awesome-skills
Maps internal link opportunities between pages with relevant anchor text, placement instructions, orphan-page detection, and cannibalisation checks.
More from mohitmishra786/low-level-dev-skills
All 138 skills in this repoARM and AArch64 Assembly
mohitmishra786/low-level-dev-skills
Guides reading and writing AArch64 and ARM Thumb assembly: compiler output, inline asm, registers, the AAPCS calling convention and NEON or SVE basics.
RISC-V Assembly Guide
mohitmishra786/low-level-dev-skills
Reference for RISC-V assembly on RV32 and RV64: register names and calling convention, extension naming, GCC and Clang inline asm, and QEMU with GDB debugging.
x86-64 Assembly Reference
mohitmishra786/low-level-dev-skills
Explains x86-64 registers, the System V AMD64 calling convention, and how to read compiler-generated or inline assembly.
Bazel for C and C++
mohitmishra786/low-level-dev-skills
Guides your agent through Bazel for C/C++ projects: BUILD files, Bzlmod dependencies, toolchain registration, remote execution, dependency queries and sandbox debugging.
Binary Hardening
mohitmishra786/low-level-dev-skills
Binary hardening skill for security-hardened C/C++ builds. An agent skill from mohitmishra786/low-level-dev-skills.
Binutils
mohitmishra786/low-level-dev-skills
GNU binutils skill for binary manipulation and analysis. An agent skill from mohitmishra786/low-level-dev-skills.
Questions about Linkers Lto
What does Linkers Lto do?
Linker and Link-Time Optimisation (LTO) skill. An agent skill from mohitmishra786/low-level-dev-skills. Linkers Lto is an agent skill from mohitmishra786/low-level-dev-skills. Linker and Link-Time Optimisation (LTO) skill.
When should I use Linkers Lto?
Linkers Lto fits situations like: configuring GNU ld; lld linker flags; diagnosing link-order issues; undefined symbols at link time.
How do I install Linkers Lto in Claude Code?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a claude-code`. Or copy the skill folder (skills/binaries/linkers-lto in mohitmishra786/low-level-dev-skills) into .claude/skills/linkers-lto in your project. Claude Code loads it when a task matches its description.
How do I install Linkers Lto in Codex?
Run `npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a codex`. Or copy the skill folder (skills/binaries/linkers-lto in mohitmishra786/low-level-dev-skills) into .agents/skills/linkers-lto in your project. Codex loads it when a task matches its description.
Can I use Linkers Lto in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitmishra786/low-level-dev-skills --skill linkers-lto -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkers-lto, .gemini/skills/linkers-lto, .github/skills/linkers-lto and .opencode/skills/linkers-lto in your project.
What does Linkers Lto need to run?
SKILL.md names no scripts, command-line tools or credentials: Linkers Lto is instructions for the agent only.
Does Linkers Lto access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Linkers Lto safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linkers Lto use?
Linkers Lto is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linkers Lto use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Linkers Lto?
Skills that share tags, products or a category with Linkers Lto: Configure Channel (openclaw/openclaw, 392k stars), Internal Links (thedaviddias/Front-End-Checklist, 74k stars), External Links (thedaviddias/Front-End-Checklist, 74k stars) and Invalid Links (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkers Lto?
mohitmishra786 (a GitHub user) maintains it in mohitmishra786/low-level-dev-skills, which has 252 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on June 27, 2026.
Source: mohitmishra786/low-level-dev-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.