Run at begin of Job execution to avoid show any secret at any step

github-actions-mask-all-secrets.yml

name: Mask secrets

on:
  workflow_dispatch:
  
jobs:
  Mask Secrets:
    name: Mask secrets at job
    runs-on: ubuntu-latest
    steps:
    - name: Mask
      env:
        SECRETS: ${{ toJson(secrets) }}
      run: echo $SECRETS | jq -r '. | values[]' | while IFS= read -r value; do echo "::add-mask::$value"; done
    - name: Use your secret
      run: |
        echo "Github Repo Secret -> FOO=value"
        echo "I'm using a secret value from Github Repo Secrets" 
        # Output: I'm using a secret *** from Github Repo Secrets

I have been asked: What happens when a secret, for example with value 1, appears in other places in the logs and it is necessary to see them? Would I see logs that say ***?
Short answer: yes.
I rephrase the question: Do you keep secrets with such short length values? Do we understand what a safe secret is?
Why do you decide to store secrets with such insecure values? Wouldn't it be more efficient to inject public environment variables instead of secret ones in these cases?